Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update RTEMS implementation to dynamically create RAM disk block devices #459

Closed
jphickey opened this issue May 13, 2020 · 0 comments · Fixed by #466 or #482
Closed

Update RTEMS implementation to dynamically create RAM disk block devices #459

jphickey opened this issue May 13, 2020 · 0 comments · Fixed by #466 or #482
Assignees
@jphickey
Labels
enhancement
Milestone
Bootes

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The current RTEMS BSP predefines the RAM disks by way of the rtems_ramdisk_configuration which is set at compile time. However the OSAL model is to create these block devices at runtime based on memory segments that are allocated externally.

The workaround up to this point was to preallocate the ram disks, and then attempt to correlate the address in the OS_mkfs/initfs request to one of the preallocated blocks. However this is not possible when the compile-time config and ramdisk allocation are done by separate libraries (BSP and CFE PSP, respectively).

Describe the solution you'd like
RTEMS can support dynamically-created RAM disks using ramdisk_allocate() which better aligns with the way things are supposed to work.

Additional context
This is necessary as part of decoupling the volume/filesystem table from the OSAL BSP.

Requester Info
Joseph Hickey, Vantage Systems, Inc.
@jphickey jphickey self-assigned this May 13, 2020
@skliper skliper added this to the 5.1.0 milestone May 13, 2020
jphickey added a commit to jphickey/osal that referenced this issue May 15, 2020
@jphickey
Fix nasa#459, dynamically create RAM disk devices on RTEMS
5f97b9b 
Rather than relying on the BSP to preallocate, the ram disk
block devices can be created based on request.  This correlates
with the way RAM disks are implemented on VxWorks and is
cleaner and more flexible by making it more independent
of the BSP.
@jphickey jphickey mentioned this issue May 15, 2020
Merged
astrogeco added a commit that referenced this issue May 26, 2020
@astrogeco
Merge pull request #466 from jphickey/fix-459-rtems-ramdisk
bc24490 
Fix #459, dynamically create RAM disk devices on RTEMS
@astrogeco astrogeco mentioned this issue May 26, 2020
Merged
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
Fix nasa#459, resolve doxygen obsolete warning
f4af70f
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
@skliper
Merge pull request nasa#460 from avan989/new_doxygen_obsolete
15ed1cd 
Fix nasa#459, resolve doxygen obsolete warning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jphickey jphickey

Labels
enhancement
Projects
None yet
Milestone
Bootes
2 participants
@jphickey @skliper