Am 25.11.18 um 22:20 schrieb Alexander Graf: > On 25.11.18 19:34, Andreas Färber wrote: >> Am 18.10.18 um 16:45 schrieb Freek de Kruijf: >>> Will there be support for the Banana Pi M64 with a more recent image? It >>> does >>> seem very complicated to have such an image available in the ports >>> repository >>> for aarch64. >> >> Please see my Wiki page: https://en.opensuse.org/HCL:BananaPi_M64 >> >> While we don't have an image for the BPi-M64 specifically (yet), you can >> derive one from JeOS-pine64 by replacing its U-Boot as described above. >> >> Note that some images like these cannot appear on the download server in >> the official places because they depend on TF-A packages not in Factory. > > Are you sure?
Yes! :) > There is an upstream U-Boot port for the M64 and I don't > see anything striking me that would require ATF modifications compared > to the Pine64. > > So it would be a good start to just try and build pine64 ATF + upstream > U-Boot compiled for M64. Why?! I packaged u-boot-bananapim64 myself (as linked in the Wiki above) and updated arm-trusted-firmware to support A64. TF-A has downstream dependencies in hardware:boot (HiKey) and therefore TF-A cannot go to Factory until those get resolved. Ideas welcome. Both hardware:boot and Contrib:Pine64 build mainline U-Boot with mainline TF-A. There is no need to use arm-trusted-firmware-pine64 anymore, it is unused now and IMO candidate for deletion if no bug reports arrive for the current A64 and H5 based U-Boot packages. Regards, Andreas > > My suggestion to you Freek would be to join us in IRC on Freenode's > #opensuse-arm channel and we'll try to figure this out together. > > > Alex -- 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]
