On Fri, May 30, 2014 at 07:59:29PM +0100, Ian Campbell wrote: > On Fri, 2014-05-30 at 17:27 +0200, Steve Langasek wrote: > > diff --git a/db/all.db b/db/all.db > > index 68f85b4..dce775d 100644 > > --- a/db/all.db > > +++ b/db/all.db > > @@ -436,6 +436,23 @@ Boot-DTB-Path: /boot/dtb > > Required-Packages: u-boot-tools > > Bootloader-Sets-Incorrect-Root: no > > > > +Machine: SolidRun i.MX 6Quad/Dual/DualLite/Solo CuBox-i Board > > +Machine: SolidRun Cubox-i Dual/Quad > > Why are there two? Are there two possible DTBs for this board or is > there some old board file style support too?
Yes, there are two DTBs: imx6dl-cubox-i.dtb imx6q-cubox-i.dtb There are four different models of cubox-i: a single core, two dual core, and one quad core variant. I'm not sure how exactly they map to the .dtb files, I've only used the quad-core one. > > +# Waits for this to be included in the kernel package > > +#DTB-Id: imx6q-cubox-i.dtb > > This is in the 3.14 kernel in Jessie now I think? Yes. > How does it work for you without? Does the firmware also embed a DTB? I > notice the script uses fdt_addr but doesn't load anything to it so I > guess something like that must be happening? I don't think the firmware embeds a DTB, it loads u-boot/SPL off of an SD card. > Is this filename the same for both of the Machine names? There are at least two .dtb files, not sure exactly how they map to actual boards. live well, vagrant
signature.asc
Description: Digital signature
