Re: Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel
On Sun, 2014-12-28 at 23:02 -0600, Robert Nelson wrote:
> On Sun, Dec 28, 2014 at 10:00 PM, Vagrant Cascadian <vagrant@debian.org> 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..
> >>
> >> 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
> >
> > Ok, so given that it might actually damage hardware to run with the
> > wrong dtb, I've written up a few UNTESTED patches to support multiple
> > DTB-Id entries:
> >
> > * copy a .dtb file to /boot in addition to the /boot/dtb-${version}
> > file, named using the ${fdtfile} variable.
>
> While reviewing I noticed one little gottcha.. This is more of a blame
> squarely at u-boot..
>
> imx targets use:
>
> fdt_file
>
> http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/wandboard.h;h=809017c5fe225278c87619e237fd0905b9c1dcf1;hb=HEAD#l140
>
> omap targets use:
>
> fdtfile
>
> Isn't that awesome. ;)
According to u-boot's README imx is in the wrong here, since only
fdtfile is documented. I think f-k should follow that lead and only
worry about fdtfile, at least until we have a concrete reason to worry
about the imx one.
Ian.
Reply to: