13 Apr
2020
13 Apr
'20
16:44
Am 13.04.20 um 12:45 schrieb Matthias Brugger: > On 4/13/20 12:19 PM, Jogchum Reitsma wrote: >>>>>> Anything I can do (not, I suppose)? >>> 1) check if the firmware blobs has such a license >>> 2) if not, talk to hardkernel to see if they can publish then under such >>> a license. >> From what I see on >> >> https://gitlab.denx.de/u-boot/u-boot/-/blob/master/board/amlogic/w400/README.odroid-n2 >> >> I think it's the files >> >> https://releases.linaro.org/archive/13.11/components/toolchain/binaries/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz >> >> and >> >> https://releases.linaro.org/archive/13.11/components/toolchain/binaries/gcc-linaro-arm-none-eabi-4.8-2013.11_linux.tar.xz >> >> Correct? And is there a specific license type you need? > > No, that's the toolchain. > > I don't know which binary files you need which Guillaume mentioned. > But normally it's something you have to 'dd' to a specific part of your > SD card so that the bootrom can load it. > > First you need to find out how to build a SD card from scratch > and then > you need to integrate that into OBS. Why would you need that? Have any of you checked the Wiki at all? https://en.opensuse.org/HCL:OdroidN2 It has a SPI flash, so you just need to locally build a decent U-Boot, flash it to SPI and boot the .iso or JeOS-efi. Unfortunately the .iso got stuck last time I tried, so someone will need to re-try with a newer kernel or debug which driver may be missing in our initrd causing this. Same problem with the VIM3 btw. Sure, making it easier for users to get a working U-Boot would be nice, but binary blobs are not the only problem here, there's also x86_64 binary-only tools from Amlogic that nobody is helping to replace. Regards, Andreas -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org