On 2020-10-27, Reco wrote: > On Tue, Oct 27, 2020 at 08:59:38AM -0700, Vagrant Cascadian wrote: >> On 2020-10-27, Reco wrote: >> > On Tue, Oct 27, 2020 at 08:02:18AM -0700, Vagrant Cascadian wrote: >> >> It looks like u-boot 2020.10 has an odroid-n2 target and >> >> arm-trusted-firmware 2.3 has an amlogic/g12a target, so it would likely >> >> be possible to enable those in the Debian packages if someone were able >> >> to test them semi-regularly. >> > >> > I happen to have an Odroid N2. What exactly such testing would require? >> >> For the debian-side of things: >> >> https://wiki.debian.org/U-boot > > That's doable. Count me in, if it's all that takes. More-or-less. :) >> And a quick guess to install would be to adapt the instructions for >> installing to use the packaged u-boot and arm-trusted-firmware (bl31): >> >> https://salsa.debian.org/debian/u-boot/-/blob/master/doc/board/amlogic/odroid-n2.rst >> >> But it will probably still require some of the components from >> hardkernel's process. > > And that one is problematic. I don't see a big problem in building > software from the source if that's required, but I prefer trusted Debian > toolchain for doing it, not some assorted Linaro blobs. In order to boot the Odroid-N2 it requires using some binary blobs from the vendor and aml_encrypt_g12a. There was work on replacing some parts for the earlier amlogic SoCs: https://github.com/afaerber/meson-tools/ But it got caught up in GPL/OpenSSL mess ... which I guess the situation has changed in Debian now... Please file bugs and/or merge requests on u-boot and arm-trusted-firmware if you want to get those parts enabled for Odroid N2 and g12a. live well, vagrant
Attachment:
signature.asc
Description: PGP signature