From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BeagleBoneBlack Updates?
Date: Sat, 14 Sep 2013 07:41:24 +0200 [thread overview]
Message-ID: <20130914074124.2e98d5db@skate> (raw)
In-Reply-To: <20130913153827.46f1c747d8fb425408b5c75b@lavabit.com>
Dear rh,
On Fri, 13 Sep 2013 15:38:27 -0700, rh wrote:
> I've heard that someone (TI) was supposed to be getting code into
> the kernel 3.12-rc series. But I saw a message recently and it looked
> like the 3.12 merge window was missed so 3.13 is the target.
A patch adding a basic Device Tree for the BBB has been posted on the
Linux ARM kernel mailing list. But the support is fairly minimal, i.e
MMC/SD is not even supported, for example.
> Some in the linux kernel aren't fond of ARM devices so maybe there's
> a logjam.
I really don't see where this statement comes from. There are
gazillions of patches being integrated to support ARM devices. I've
myself worked over the last year on upstreaming the support for some
ARM processors, and while it certainly requires some work, I clearly
don't think there is some resistance against ARM devices at all.
> But I've also been told that it's due to lack of resources at
> TI.
I believe this is more the problem. TI already had issues getting the
complete support for their SoCs merged in mainline (due to the
complexity of their SoC, and also probably due to the internal
organization of TI), but now TI has laid off a huge number of
engineers, including some of which where working on upstreaming work.
So there's even less work force in TI to do this work.
And on the other hand, the CircuitCo guys have not tried at all to
submit any of their patches to mainline (the Device Tree patch
mentioned above being the first one). Their excuse is that they have
been having issues to cooperate with TI on upstreaming effort, but when
we see how long it takes TI to bring stuff in mainline, there is
certainly room for others to contribute. However, I admit it is hard to
do mainline work when the SOC vendor is also doing something, but you
don't know what.
> So maybe BBB will truly be a DIY platform. The problem that exists
> is that using the wrong device tree code can result in destroying devices.
> It seems that some people have done that and blown up their HDMI
> interface.
This is if you use the mainline kernel. The BBB defconfig in Buildroot
will use the BBB-custom kernel provided by CircuitCo, because we should
certainly offer to our users a kernel that allows to use as many
features as possible of the BBB.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-09-14 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 12:58 [Buildroot] BeagleBoneBlack Updates? Frank Hunleth
2013-09-13 14:39 ` Zoltan Gyarmati
2013-09-13 15:15 ` Jesse Cobra
2013-09-14 5:33 ` Thomas Petazzoni
2013-09-16 1:16 ` Frank Hunleth
2013-09-16 9:06 ` Greg Beresford
2013-09-16 9:41 ` Frank Hunleth
[not found] ` <20130913153827.46f1c747d8fb425408b5c75b@lavabit.com>
2013-09-14 5:41 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130914074124.2e98d5db@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox