Re: new A64-OLinuXino revisions

[Andre Przywara <andre.przywara@arm.com>]

Hi Roman,

many thanks for reaching out!
I take it you are not directly involved with the vendor, but since you 
are here, I am going to ask you all those questions ;-)
CC:ing Stefan, not sure this still works, his last mainline patch was a 
while ago.

On 4/24/26 11:25, Roman Riabenko wrote:
> Hello.
> 
> The vendor revised A64-OLinuXino and released additional devicetrees.

Well, "released" should be done via sending to the kernel mailing list, 
getting them reviewed and then merged. But well...

> Mainline Das U-Boot and Linux support revisions C and D. However,
> revision E and later require the vendor devicetree files to operate
> properly. For example, RX delay is required for stable download. There
> are also changes to voltages. Vendor's local changes to the kernel may
> need to be considered too.

So does one vendor devicetree support all versions? Or do they patch 
something, either when installing or at each boot time?
Do you have any board of older revisions, by any chance, so that you 
could run some tests?

And do you have a list of exact changes between revisions? Is there some 
changelog somewhere on the Olimex site or repo?
Also I see that the Olimex OSHW repo lists revisions up to H already.

> The vendor u-boot repository has old devicetrees only. The vendor also
> provides a single customised Debian image for all A64-OLinuXino, which
> does some initial board-specific setup at first boot.

So is there a way to detect those revisions? There is precedence in 
mainline U-Boot for patching DTs on the fly for board revisions, so we 
could apply required changes there. But we would need some way to check 
which version this board is. Are there some GPIOs or so for this? 
Sometimes there are other means of detection, like SPI or I2C device 
presence or something.

> I would like to start a discussion about how to have these changes
> mainlined.
> 
> For your immediate reference, I attach the patch obtained from the
> GitHub commit changing devicetrees.

So this one seemingly ignores the mainline devicetrees, instead installs 
their own versions? I would have hoped they would at least adjusted or 
included the mainline DTs ...

Cheers,
Andre