[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel

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 <vagrant@debian.org> 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?

> > 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.

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"

> These might be a bit invasive for this point in the release cycle, but
> they also aren't terribly large patches...  I can do some further
> testing if it seems like the approach is worth pursuing at this point.

It is a little bit invasive, I was hoping not to be making large changes
(i.e. anything more than db updates) to f-k at this point. But perhaps
it is the best we can do.

Given the beaglebone specific findfdt which Robert links to above could
we add a check to bootscr.beaglebone which refuses to boot on a white?
(looks like we can look at $board_name directly).


Reply to: