Additional, 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. Tony On Mon, Apr 24, 2017 at 10:35 AM, Tony Su <tonysu@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?
Thx, Tony
On Mon, Apr 24, 2017 at 10:33 AM, Andreas Färber <afaerber@suse.de> wrote:
Hi Tony,
Am 24.04.2017 um 19:19 schrieb Tony Su:
Hi, I'm looking for the referenced Wiki with links to dtb overlays, can't find it.
For that matter, I can't find the specific github repo (Is the Wiki associated with the github project or some other Wiki?)
Looking around, I can only find the following HCL page that lists supported HATs which is something I haven't noticed before. https://en.opensuse.org/Category:Raspberry_Pi_40-pin_connector
Look at the ArPi600 link in that category, for instance.
For Chistera Pi and TLV493D there are overlay files too, but no links in the Wiki yet.
The Arduino Shield, MikroBus and XBee categories should also have some.
The commands can either be typed manually or placed in a boot.script that then needs to be turned into boot.scr via mkimage (u-boot-tools) and placed into the first partition (i.e., /boot/efi if it exists, /boot otherwise).
Regards, Andreas
-- 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@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org