Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5601
Assignee: Gedare Bloom ## Summary The RTEMS FDT is a wrapping API for `libfdt` and currently it is mostly a fairly thin wrapper. However, we could make the RTEMS FDT handle the endianness encoding/decoding for translating values back and forth between the user and the `libfdt`. ### Purpose <!-- Why do you specifically need this feature and how would it be useful for others --> Currently a user has to know to call the endianness conversion functions if they have/need values in little-endian format, because the FDT format is big-endian. By hiding the endianness conversion within the RTEMS API we can greatly simplify the application (and BSP) logic for working with FDTs. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5601 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
