On Thu, Apr 16, 2020 at 3:14 PM Derek Atkins <derek(a)ihtfp.com> wrote:
On Thu, April 16, 2020 10:01 am, Peter Robinson wrote:
>>
>> So where is this Rev B1 coming from? Why does it not know it's a Rev D1
>> board? This is clearly causing it to pull in the wrong DTB file, which
>> explains why it isn't working.
>
> It's the last option in the statement check in board detection which
> means it's basically the board of last resort. so it seems your rev of
> the D1 isn't being detected, there was initial support for the revD1
> land upstream in U-Boot in Oct 2017.
*sigh* I acquired this board only a few months ago.
I tried doing a "setenv" within uboot to change the board-name from B1 to
D1 but obviously that didn't do anything since I think it needs to be
It'll be using a GPIO or availability of something to detect the board
so that won't make any difference.
detected earlier than that. So this requires a change to u-boot? I
must
admit that I've never looked at uboot code so not even sure where to start
to see where I would need to add something for my board, let along figure
out what it is I need to add. (Well, I suppose once I figure out what
it's looking for I can hopefully probe the board to figure out what it's
saying).
Why can't they make this easy? :(
The proper question is why is Wandboard hostile to upstream by not
sending their device support upstream. The original commit was by a
NXP maintainer, but there's been little on the Wandboard stuff at all
since the addition of the D1 support.
> -derek
>
> --
> Derek Atkins 617-623-3745
> derek(a)ihtfp.com
www.ihtfp.com
> Computer and Internet Security Consultant
>