-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate network logic in pc-rtems to support generic targets #375
Labels
enhancement
New feature or request
Comments
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The only non-generic implementation in pc-rtems is the network setup, which prevents use on a generic target.
Describe the solution you'd like
Isolate/separate network setup to support source selection or similar configuration option. Consider configuring from target defs or similar to avoid changes required within psp.
Describe alternatives you've considered
Could make an additional psp, but doesn't seem worth duplicating all the pc-rtems code that isn't specific to pc's.
Additional context
Specific parts:
PSP/fsw/pc-rtems/src/cfe_psp_start.c
Lines 36 to 40 in a260e9c
PSP/fsw/pc-rtems/src/cfe_psp_start.c
Lines 67 to 84 in a260e9c
Might also benefit from making /mnt/eeprom a config param... depends on how/where this is actually set up by the PSP. Would be nice to shift away from "eeprom" and use generic "nonvol".
Requester Info
Jacob Hageman - NASA/GSFC
The text was updated successfully, but these errors were encountered: