Am 24.04.2017 um 19:43 schrieb Tony Su:
It's been a few months since I looked at this,
Raspbian makes it very easy (?) to add definitions, you drop
individual files for each definition into a directory, then boot.
I didn't explore how difficult it would be to write the definitions themselves.
Of course, if the dtb definitions are identical, then it would mean
that just dropping the files from raspbian into the openSUSE directory
would instantly enable support for the 50-plus or so HATs (last I
counted) that Raspbian supports.
On Mon, Apr 24, 2017 at 10:35 AM, Tony Su <tonysu(a)su-networking.com> wrote:
> Are you using the same dtb definitions and format as what is being
> used in the Debian Raspbian image which does <not> use u-boot?
Reminder: Please don't top-post on our mailing lists; reply below.
openSUSE uses U-Boot, and U-Boot does not get its Device Tree from the
Raspberry Pi firmware, so their built-in overlay support (config.txt) is
useless to us.
Whether it would be possible to iterate over files in a directory from a
U-Boot script I haven't tried, can't think of how - if you have a
solution, please share.
The alternative would be to do it as a systemd service from Linux, but
that would require some DT merging tool AFAIU, which we don't have
today. That's why reusing U-Boot's existing implementation is somewhat
convenient for me, even if sub-optimal.
As for reusing Raspbian .dtbo files, any .dtbo file always depends on
the base .dtb file. So if they are still based off old non-mainline
bcm2708/09/10 files, then reusing them with mainline bcm2835/36/37 files
is unlikely to work.
section 2.1 also mentions differences between -overlay.dtb and .dtbo for
(their?) kernel v4.4+.
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org