Am 11.12.2017 um 21:47 schrieb Andrew Wafaa: > On 11 December 2017 at 20:23, Andreas Färber <[email protected]> wrote: >> Am 11.12.2017 um 14:22 schrieb Alex Naumov: >>> do we want to integrate everything what Pinebook needs to our TW >>> images OR we would like to have separate images for it? >> >> I don't think it's possible to combine the Pinebook into an existing >> image, as it likely needs its own U-Boot with matching Device Tree. >> >> That leaves us with two options: >> >> a) Derive a new separate image once all needed packages are in place. As >> long as arm-trusted-firmware is not in Tumbleweed, such an image can >> only live in some Contrib repository, not officially part of Tumbleweed. >> > > Is there a particular reason why arm-trusted-firmware isn't in > Tumbleweed yet? Sorry but I missed any previous discussion on ATF.
Short summary: U-Boot is in Base:System devel project and for some boards now has a soft dependency on ATF - builds okay but won't work. Base:System has so few maintainers and keeps blocking and rebuilding packages (due to core packages such as glibc), that we've already resorted to Base:System:Staging for actually being able to test new sub-packages and updates. So I really don't want to submit my ATF packages to Base:System. Additionally, Andre did not yet get his Allwinner A64/H5 support merged into upstream ATF, so an arm-trusted-firmware package today would only help e.g. Firefly-RK3399 and Geekbox, not Pine64 or Orange Pi PC 2. One proposed idea was a new sub-project under "hardware" (where u-boot or arm-trusted-firmware don't fit 100%, I'm surprised vboot was accepted despite not being about peripherals), but so far we haven't discussed any names or alternative locations. Opinions? 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]
