Bug#824399: Missing devicetree statements for ARM

[Dimitri John Ledkov]

On Sun, 15 May 2016 15:45:25 +0200 "Steinar H. Gunderson"
<sgunderson at bigfoot.com> wrote:
> Package: grub-common
> Version: 2.02~beta2-36
> Severity: normal
>
> Hi,
>
> I'm setting up GRUB on my ODROID XU4 (chainloading via U-Boot).
> It actually works surprisingly well, but grub-mkconfig has one
> serious omission; it doesn't load the device tree, which causes
> the kernel not to boot.
>
> I suppose the right way to deal with this is to patch /etc/grub.d/10_linux
> to not only look for initrds but also device trees; the logic is
> extremely similar. I believe flash-kernel copies these into place
> (from /usr/lib/linux-image-<version>/), but it also adds its own
> boot.scr which overrides GRUB chainloading from U-Boot, so maybe
> some adjustments need to be made there.
>
> For the record, here's a typical boot sequence for my XU4 if I boot
> it manually:
>
>   set root=(hd0,msdos1)
>   linux /vmlinuz-4.5.0-2-armmp-lpae root=/dev/mmcblk1p2 ro init=/bin/systemd
>   initrd /initrd.img-4.5.0-2-armmp-lpae
>   devicetree /dtb-4.5.0-2-armmp-lpae
>   boot
>
> where /dtb-4.5.0-2-armmp-lpae is a symlink (created by flash-kernel)
> into dtbs/4.5.0-2-armmp-lpae/exynos5422-odroidxu4.dtb. I would assume
> just checking for /dtb-<version> would be a very good start.
>
> Thanks!

I have now provided a patch to support devicetree command and load
dtbs as extracted by flash-kernel at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929427
Also trying to get it applied upstream.

Regards,

Dimitri.