On August 20, 2014 2:09:01 AM CDT, Ben Gras <b...@shrike-systems.com> wrote:
>All,
>
>I'd love the Beagle BSP. I am fighting to find time to polish it,
>re-test it, and re-submit the patches.
>
>To decide whether that's feasible, is freezing the code for the release
>'any day now' or more like 'any week now'?
>

It won't be this week. I would like it to be ASAP but know we have some tidying 
up to do.

Has the BSP at least been posted for initial review? Is it warning free? Small 
updates are easy to review.
>
>On Tue, Aug 19, 2014 at 11:43 PM, Joel Sherrill
><joel.sherr...@oarcorp.com> wrote:
>
>
>On 8/19/2014 4:34 PM, Chris Johns wrote:
>> On 20/08/2014 2:38 am, Gedare Bloom wrote:
>>> Anything holding it up at the moment?
>> It would be good to get a formal tool set definition into
>rtems-tools.git.
>>
>> I am currently testing a change to newlib 19-Aug-2014 which removes
>an
>> old patch we had.
>
>We need to make sure that we are on a path for the RSB, Debian and RPMs
>to come
>from the same tool versions and patches.
>
>Also there is likely a todo list for RTEMS itself. Not sure what that
>is
>off the top
>of my head but a few items:
>
>+ Merge Beagle BSP
>+ Merge pending GSOC work
>+ 386 context switch SMP synchronization is not right. Others were
>updated.
>
>What's the status of the dynamic loader? I suspect it is on its own
>independent
>release arc.
>
>
>
>> Chris
>> _______________________________________________
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>--
>Joel Sherrill, Ph.D.             Director of Research & Development
>joel.sherr...@oarcorp.com        On-Line Applications Research
>Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>Support Available                (256) 722-9985
>
>
>_______________________________________________
>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

Reply via email to