On Sat, Aug 8, 2020 at 1:54 PM Chris Johns <chr...@rtems.org> wrote: > On 8/8/20 6:01 pm, Niteesh G. S. wrote: > > ping. > > I am sorry about the delay in answering. It is the weekend so things can be > slow. I will add some input to see if we can figure this out. I have not > followed all the discussions in detail so please correct me if I have > taken a > wrong turn. > > > On Wed, Aug 5, 2020 at 12:16 AM Christian Mauderer <o...@c-mauderer.de > > <mailto:o...@c-mauderer.de>> wrote: > > > > Hello, > > > > I think the big question is: Should we make that a public API and > keep > > it in cpukit or should we make it a BSP support code and move ti to > the > > bsps/shared section? > > > > Sebastian and Gedare: Like Niteesh said: There have been some > different > > directions in the past. Which one should be the target? > > I spent some time this week looking into these functions and I cannot any > other > implementation or use for functions starting with OF_*. They seem very > specific > and related to BSD Unix. > > These are low level and board related rather than an core interface so this > would tend to make then reside in the BSP shared area. > > Are there BSP or architecture specific parts in the implementation detail? >
We only care about the FDT implementation for the OF interface so I don't think we will have any BSP or architecture-specific parts since the implementation will only be dependent on the device tree and it is well standardized. Are there any architecture-specific device tree properties? AFIAK the OFW FDT implementation in FreeBSD does not contain any architecture-specific implementation. > Thanks > Chris >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel