Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel
On Mon, Dec 29, 2014 at 7:13 AM, Ian Campbell <firstname.lastname@example.org> wrote:
> On Sun, 2014-12-28 at 20:00 -0800, Vagrant Cascadian wrote:
>> On 2014-12-28, Robert Nelson wrote:
>> > On Sun, Dec 28, 2014 at 6:26 PM, Vagrant Cascadian <email@example.com> wrote:
>> >> On 2014-12-28, Ian Campbell wrote:
>> >>> OOI, do you know how broken the white is when booting with the black's
>> >>> DTB? Completely unusable, missing some minor peripheral or somewhere in
>> >>> the middle?
>> > Oh you definitely don't want to run the wrong *.dtb on the black/white..
> Is it dangerous both way around or only dangerous to boot the black dtb
> on the white?
A quick scan of the dtb's.. The microSD would be limited to 1.8v (3.3v
removed), so users could find themselves with a broken boot if they
booted am335x-boneblack on a classic bone.
>> > In u-boot the findfdt function will correctly set the fdtfile variable.
>> > http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/am335x_evm.h;hb=HEAD#l176
>> > Notice:
>> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am335x-boneblack.dts?id=2ba3549352277514a8e4790adff77a783ee1b9e2
>> > IMPORTANT: booting the existing am335x-bone.dts will blow up the HDMI
>> > transceiver after a dozen boots with an uSD card inserted because LDO
>> > will be at 3.3V instead of 1.8.
>> > Also the 'white' uses DDR2, while the 'black" uses DDR3
> Is white==am335x-bone.dts or is there a third unsuffixed variant too? (I
> think the answer is no, but I'm not sure). I'm wondering if we should
> try to upstream a patch to make the white also unambiguously identify
> itself as such, by adding White to the model and the dts name.
Officially by beagleboard.org they've always been called:
BeagleBone : am335x-bone.dtb
BeagleBone Black : am335x-boneblack.dtb
Unofficially, the community started calling the original BeagleBone as
the 'white' as the number of users with 'Black''s massively out number
the 'white'... Confusion entailed..
There's also the "blue" oem version, which is just the "black" with a
few oem changes, but uses the black's eeprom id...
> Did we support Beaglebone* in Wheezy or is it all new in Jessie (IOW to
> what extent can we fudge the upgrade path and just "rip the plaster off"
The beaglebone's were not truly usable on mainline till v3.11-rc or
so, due to the edma/dma engine changes needed to support the mmc