Happy to see this but a bit concerned that there is only one architecture's BSPs addressed. What about the other architectures?
--joel On Thu, Mar 23, 2023, 12:07 PM Chris Johns <chr...@rtems.org> wrote: > On 24/3/2023 3:57 am, Sebastian Huber wrote: > > On 23.03.23 17:52, Will wrote: > >> Great idea to store this information in the executable itself. Does > this need > >> a RTEMS_TEST_STATE_LINK_ONLY test state or something similar for > minimum.exe? > > > > With the notes you can build the test. The test runner would look at the > notes > > and then decide if it makes sense to run the test or not. It could still > run the > > minimum.exe and see if it terminates. > > I welcome notes support. Thanks for adding it. > > How will we control and manage the notes we support? > > Should we document the top level notes domains (?) with some we control and > restrict and others users can use? For example `note.rtems.test`, > `note.rtems.kernel`, `note.rtems.bsp`, and `note.rtems.user`? > > Do you have any host side tools in mind to access notes apart from the > standards > like readefl? Maybe the rtems-exe-info tool could do this? > > 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
