attaching an interrupt in beaglebone bsp

Ben Gras beng at shrike-systems.com
Wed Jun 3 15:13:08 UTC 2015


On Wed, Jun 3, 2015 at 4:23 PM, Gedare Bloom <gedare at rtems.org> wrote:
> On Wed, Jun 3, 2015 at 10:04 AM, Ben Gras <beng at shrike-systems.com> wrote:
>> All,
>>
>> On Tue, Jun 2, 2015 at 1:28 AM, Chris Johns <chrisj at rtems.org> wrote:
>>> On 1/06/2015 6:06 pm, Ben Gras wrote:
>>>>
>>>> This tutorial covers everything from scratch and I recently verified the
>>>> instructions work & the built result works :).
>>>>
>>>> http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html
>>>>
>>>
>>> What is outstanding and needs to be merged ?
>>>
>>> Do Trac tickets exist ?
>>
>> Hi Chris,
>>
>> I have a large-ish commit for RSB that builds qemu, uboot and some FS
>> utilities. This is so a full FS image can be made with provided tools.
>> It wasn't merged because of uboot and its license so in my mind this
>> is blocking on a replacement becoming available.
>>
> I don't personally see a problem with providing a way to build uboot,
> although if Chris opposed it that is good enough for me.
>
>> In rtems-tools I have a tester to run the test set using qemu, but
>> this depends on changes in RSB.
>>
>> Should I open tickets for them even though they're blocked?
> Yes. You can also provide them in a fork of RSB if you care to
> maintain such a thing.

I actually do have forks of RSB and rtems-tools with the required
changes on my github repo's. I'm quite eager to merge them mainline
though because occasionally the build breaks if RSB updates are
needed.

The RSB change:
https://devel.rtems.org/ticket/2359

The rtems-tools change:
https://devel.rtems.org/ticket/2360



More information about the users mailing list