The part about testing with a simulator is vague. But you can go ahead and generate tasks. Create 1 task per architecture that remains, and allow 5 instances for each.
On Tue, Jan 5, 2016 at 4:17 PM, Joel Sherrill <j...@rtems.org> wrote: > > > On Tue, Jan 5, 2016 at 2:39 PM, Gedare Bloom <ged...@rtems.org> wrote: >> >> On Tue, Jan 5, 2016 at 3:11 PM, Joel Sherrill <j...@rtems.org> wrote: >> > >> > >> > On Tue, Jan 5, 2016 at 1:33 PM, Gedare Bloom <ged...@rtems.org> wrote: >> >> >> >> >> It might be good to create GCI tasks for students to get RTEMS >> >> >> Tester >> >> >> working for a few simulator targets that are supported? >> >> >> >> >> > >> >> > I could be wrong but I think I created them for all gdb based >> >> > simulators. >> >> > There is unlikely much low hanging fruit. >> >> > >> >> I just meant a task to run the Tester for some target that is a >> >> candidate for the follow-on work. That gives the potential students a >> >> baseline. >> > >> > >> > Oh... I actually wrote a task for a GCI student to do this. :) >> > >> > https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs >> > >> > What do you think? >> > >> Save the page? > > > Sorry. I am glad I didn't lose it in that length of time. I am still at home > for the holidays and had to find a cat in the attic and then take a shower. > :( _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
