Barebox 2020.01.0 and Device Tree from Linux Kernel 5.4

[gianluca <gianlucarenzi@eurek.it>]

Hello list!

I was wondering if the device tree from (latest) Linux Kernel can be 
used when building Barebox 2020.01.0 for iMX6 compatible custom board.

For sure the include path and other stuff are quite different (kernel 
and barebox), so I am pretty sure it will fail to build with some sort 
of "foreign" device-tree. Another issue, will be the drivers to have 
full access from Barebox-Point-Of-View. If the device-tree properties 
and compatible strings are quite different, Barebox will fail to 
activating/probing/using the internal driver.

So I am asking:
There is a "official" way to manage those differencies?

Am I forced to use TWO device-tree dts files (almost identical each 
other) ???

It seems it is like re-inventing the wheel...

I think this procedure can be used with ALL supported boards present in 
barebox source tree.

Actually I am using a slightly modified device-tree for my boards from 
kernel, then adapted to be compiled for Barebox.
Some nodes are "disabled" by default as status, so Barebox will activate 
them when probing the real-hardware.

I would like to keep my code to activate/deactivate device-tree drivers, 
but without modifying the Kernel device-tree each time when I do a 
Kernel update.

Any hint will be very accepted.

Regards,
-- 
Eurek s.r.l.                          |
Electronic Engineering                | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy  | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377  | Fax:   +39-(0)542-609212

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox