Wayne Thornton commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5430#note_140285 I'm currently working on this issue with a proposed implementation. There are some issues with licensing as the upstream EEFS driver is licensed under the NOSA (NASA Open Source Agreement) which is not strictly BSD compatible. This necessitates (in my opinion) a complete rewrite and implementation to the EEFS technical standard, which can be located here: https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fraw.githubusercontent.com%2Fnasa%2Feefs%2Frefs%2Fheads%2Fmaster%2Fdoc%2FEEPROM%2520File%2520System%2520Design%2520Notes.docx&wdOrigin=BROWSELINK I've currently gotten a skeleton build worked out in my private fork and I'm able to get a build to compile. I've added CONFIG_FILESYSTEM_EEFS and RTEMS_FILESYSTEM_TYPE_EEFS defines to the cpukit/rtems/include/confdefs/libio.h and cpukit/rtems/include/libio.h where needed and created a libeefs.yml and updated the grp.yml file in cpukit/libfs. There's a lot of work left to do, especially to meet the standard, so if anyone has insights into the best way to implement a new filesystem as RTEMS-native that would be appreciated! I'm available on Discord (@thornwm or Publius4079) either direct message or in the channels. If you've got time for a voice chat, that would be helpful! -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5430#note_140285 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
