[Buildroot] Beaglebone Black support

Charles Krinke charles.krinke at gmail.com
Sun Jun 23 23:23:56 UTC 2013


In the case of the Linux kernel, official means kernel.org and nothing TI
or any other group or organization does is "official".

If TI wishes their patches accepted into the kernel along with everyone
else, they must play by the same rules.

Charles
On Jun 23, 2013 4:20 PM, "rh" <richard_hubbe11 at lavabit.com> wrote:

> On Sun, 23 Jun 2013 15:21:04 -0400
> Frank Hunleth
> <fhunleth at troodon-software.com> wrote:
>
> --8<--
>
> > However, copying the patches over to buildroot seems wrong and painful
> > to maintain, but as far as I can tell, there's no official/maintained
> > git repo with the beaglebone.org kernel patches.
>
> This seems official to me but not sure what you mean by official.
> Do you mean kernel.org-official?  TI-official? Circuitco?
>
> https://github.com/beagleboard
>
> > I was wondering if there were any thoughts about a nice way to handle
> > this... or has anyone already done this, but not submitted their
> > patches?
>
> Far as I can tell the ARM community has embarked on using device tree
> and I think that work's underway. But I'm new to the BBBlack and
> ARM hardware.  From what I've gleaned here and there, using the device
> tree is a prereq for getting upstream with the BBB code.
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130623/aed4c7ed/attachment.html>


More information about the buildroot mailing list