Hi Sid, Am 18.04.2017 um 21:35 schrieb Sid Boyce: > On 15/04/17 09:48, Andreas Färber wrote: >> Amlogic S905 MMC support has just landed in U-Boot last night, allowing >> to finally migrate my two S905 devices over to our openSUSE kernel. >> >> Am 11.04.2017 um 01:42 schrieb Andreas Färber: >>> == aarch64 == >> Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] > Which image boots on the ODROID-C2?
Short answer: None, I have not created a JeOS image yet. Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. (https://build.opensuse.org/request/show/487710 is still pending for the previous v2017.03...) -rc2 still does not include all patches for a convenient boot from SD - we could queue some in our package of course. Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib. Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+. Cf. https://en.opensuse.org/HCL:OdroidC2 So... would it help to create a JeOS image without the bootloader? You could then dd the bootloader onto the SD card in a second step. The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD. I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2 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: [email protected] To contact the owner, e-mail: [email protected]
