On Mon, 2014-02-24 at 14:41 +0100, Jasmin Schnatterbeck wrote: > Package: flash-kernel > Version: 3.13 > Severity: important > > The device DB is missing support for the Mirabox. > > Proposal:
Thanks for this. Perhaps you could also add some information to http://wiki.debian.org/DebianOn ? > Machine: Globalscale Mirabox > Kernel-Flavors: armmp > DTB-Id: armada-370-mirabox.dtb > DTB-Append: yes Is this really required on new platform like this? I would expect that a newish system would have a u-boot which supports FDT natively rather that via appending. Does loading the dtb at some address and adding that address as a third argument to the "bootz" or "bootm" command work? On the other hand you say the u-boot is quite old so maybe this is correct, I just wanted to check that you didn't just copy this bit from an older platform. > U-Boot-Kernel-Address: 0x00008000 > U-Boot-Initrd-Address: 0x0 > Boot-Device: /dev/sdb1 > Boot-Kernel-Path: uImage > Boot-Initrd-Path: uInitrd > Boot-DTB-Path: dtb > Required-Packages: u-boot-tools > Bootloader-Sets-Root: no This is now called Bootloader-Sets-Incorrect-Root. > Even kernel 3.13. does not support the device's internal > NAND chip - /dev/sdb is the microsd-slot of the device which can be used > as rootfs. > Bootloader is u-boot (heavily modified by the manufacturer and fairly > old) with unusable ext2load (at least for ext4), so separate boot > partition /dev/sdb1 for fatload makes sense. OOI do you know if mainline u-boot getting any support for this device (whether based on the vendor's version or not)? Ian. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
