On Fri, 29 Oct 2021 at 01:37, Joel Sherrill <j...@rtems.org> wrote: > > On Thu, Oct 28, 2021, 6:25 PM Chris Johns <chr...@rtems.org> wrote: > > > On 29/10/21 6:26 am, Joel Sherrill wrote: > > > On Thu, Oct 28, 2021 at 12:20 PM Hesham Almatary > > > <hesham.almat...@cl.cam.ac.uk> wrote: > > >> > > >> Does RISC-V need that too? > > > > > > Not based on the current bsets. > > > Right, it is required only for Spike, which uses devel/dtc pointing to DTC 1.4.1 version. https://github.com/RTEMS/rtems-source-builder/blob/master/bare/config/devel/spike.bset#L7
> > > $ grep -r dtc * > > > 6/rtems-moxie.bset:devel/dtc-1.6.0-1 > > > 6/rtems-microblaze.bset:devel/dtc-1.6.0-1 > > > 7/rtems-moxie.bset:devel/dtc-1.6.0-1 > > > > > > Alex.. the grep shows that 7/microblaze is out of sync. Please address > > that. > > > > > > Hesham.. if riscv needs dtc, it should be added to its bset for 6 and 7. > > > > Should we add DTC to the default package set and avoid the need to manage > > what > > needs it? > > > > The rational is the growing use of FDT in RTEMS and this lets us control > > what we > > need on a per release basis. For example 5 years from now DTC has changed > > and > > RTEMS today does not work with it. > > > > I think that is a really good idea. DTC broke a handful architecture tools > when it wouldn't build on FreeBSD 13. If we had to build it for every > architecture oh, then it would have gotten addressed quicker. > > And your logic that is a commonly used tool is also quite true. It isn't a > huge burden. > > Perhaps Alex can do this as a follow-up patch after this > > --joel > > > > > Chris > > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
