From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vagrant Cascadian Date: Thu, 14 Feb 2019 08:51:46 -0800 Subject: [U-Boot] mx6cuboxi: Detecting wrong .dtb (v2019.01) In-Reply-To: <87pnrusn6a.fsf@tarshish> References: <87o97f639q.fsf@ponder> <87va1mstrf.fsf@tarshish> <87bm3e67y3.fsf@ponder> <87pnrusn6a.fsf@tarshish> Message-ID: <877ee25n4t.fsf@ponder> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 2019-02-14, Baruch Siach wrote: > On Thu, Feb 14 2019, Vagrant Cascadian wrote: >> On 2019-02-14, Baruch Siach wrote: >>> On Wed, Feb 13 2019, Fabio Estevam wrote: >>>> On Wed, Feb 13, 2019 at 2:52 PM Vagrant Cascadian wrote: >>>>> >>>>> I *think* this board is getting the wrong fdtfile set: >>> >>> What hardware are you running? Is it a Cubox-i? >> >> Cubox-i4x4. >> >>> What is your actual problem? >> >> Before v2018.07: fdtfile=imx6q-cubox-i.dtb >> >> in v2018.07: fdtfile=imx6q-cubox-i-som-v15.dtb >> >> as of v2019.01: fdtfile=imx6q-cubox-i.dtb >> >> I am not sure which is actually correct, but since it switched once, and >> then switched back, I figured it was a regression. It appears to run ok >> with either .dtb file, though maybe some features I don't use might not >> work correctly. > > Only fdtfile=imx6q-cubox-i.dtb is correct. Cubox-i never shipped with > SOM rev 1.5. So it looks like a bug in v2018.07. > > The kernel has -v15.dts files for Cubox-i only because Russell King has > a few experimental samples for that combination. Ok, thanks for confirming and setting my confusion to rest. live well, vagrant -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: