From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx6cuboxi: Detecting wrong .dtb (v2019.01)
Date: Thu, 14 Feb 2019 08:51:46 -0800 [thread overview]
Message-ID: <877ee25n4t.fsf@ponder> (raw)
In-Reply-To: <87pnrusn6a.fsf@tarshish>
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 <vagrant@debian.org> 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: <http://lists.denx.de/pipermail/u-boot/attachments/20190214/71e06858/attachment.sig>
prev parent reply other threads:[~2019-02-14 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 16:50 [U-Boot] mx6cuboxi: Detecting wrong .dtb (v2019.01) Vagrant Cascadian
2019-02-13 17:02 ` Fabio Estevam
2019-02-14 7:40 ` Baruch Siach
2019-02-14 9:22 ` Vagrant Cascadian
2019-02-14 10:02 ` Baruch Siach
2019-02-14 16:51 ` Vagrant Cascadian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ee25n4t.fsf@ponder \
--to=vagrant@debian.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.