TI Supports their kernel at
which contains linux-3.12
Angstrom is based on openembedded-core and meta-openembedded, but is not using the standard repos.
You need to check out the Yocto-1.5 branch to get access to the latest stuff though.
If you clone the master, you do not see much development,since this is based on Yocto-1.3 which sees little development.
Buildroot is not Yocto compliant, which means that they will not follow mainstream development funded by large companies.
Where is this documented? And why should I care? The above two paragraphs are unintelligible to anyone that hasn’t been involved in embedded Linux for some time.
With the greatest respect to Gerald, Robert and the others who are doing a heroic job and whoever else was involved in designing a very, very nice piece of hardware, the software support is poor. I’m sure this will change at some point but as of today I can choose from a kernel that tends to hang with USB devices (3.8, shipping) or a kernel that doesn’t work with capes (3.12 or 3.13rcN). Both are from Robert via a wiki (elinux.org) which isn’t associated with the beaglebone website, and it appears he’s the only guy working on it. Yet there are apparently several thousand Beaglebones shipping a month?!? That’s just crazy.
As for Angstrom, every time a question comes in about “how do I configure this” I wonder why a debian-based distribution wasn’t chosen: it would halve the number of messages to this list, and reduce most of the rest to a link to someone else’s documentation.
No matter what people tell you, BBB is very very very far from the Raspberry Pi’s software quality and its huge community.
CircuitCo and TI advertise the BBB wherever they can but their promises are far from reality.
Why does CircuitCo still advertise their LCDs as working with latest Angstrom after all the discussions I had with them here in the groups?
Many people here tell you that everybody should learn Linux at bare metal level and should be able to write his own kernel drivers to get simple things done. I don’t agree,
I agree with this 100%. I really, really don’t want to sound sour and I’m very grateful for the support I’ve received on this list, but it feels like there should be an organization with resources backing the Beaglebone, and they’re just not there.
So like all the whining about how circuitco and x-y-z needs to get busy doing drivers for x-y-z feature. I dont know where you guys have been for the last 6-7 months but I have yet to find much of anything that does not work with the BBB. SO the SGX/DRM drivers dont work . . .BFD this is not a computer platform but an embedded system platform.
USB hotplug doesn’t work under 3.8.13, and USB devices tend to crash or hang the kernel - my experience, but it appears form this list I’m not alone. USB works for me with 3.12, but capes do not as the pins can’t be remuxed (terminology?) Again, my experience but I believe I am correct and posted my testing results here a few weeks ago.
I believe there is no kernel currently available for download that offers reliable USB hotplug and supports capes, and if anyone can correct me on that with a link to one I would be overjoyed.
Seems to me that some of you could apply yourselves more to get whatever it is you wish to work with the hardware. especially considering the cost of the hardware is so small.
The “if you’re not happy why don’t you fix it yourself” appeal to open-source rebuttal is a very old one and I’m not sure it flies in this case. Debugging the kernel is beyond most. Athough I’ll agree 2 minutes with google might have saved a bit of traffic on this list…
Myself, I was hoping to leverage the platform the BB provides and build on it, rather than spend my days debugging the platform. I’m very experienced with Linux and yet I’m still waiting on someone else to supply a fix; every time I see a message that starts “I’m new to Linux and BBB but I want to do X” I wince, as I know there’s many months of poorly charted territory ahead for someone.
Hope that didn’t come across as too ranty. I really just wanted to agree with Anguel but got carried away.