[opensuse-arm] Support for Hardkernel Odroid N2
Hi, Are there any plans/is there any progress of enabling opensuse TW or Leap for the Hardkernel Odroid N2? I can't find anything on this list about that, and the last message about this I've seen is on the forum, https://forums.opensuse.org/showthread.php/536160-Initial-success-running-Le... The last post on that thread is almost a year ago (May 28, 2019) I've two of them now, both running Ubuntu, and ordered two more at Hardkernel; could take a while before they arrive. But I could do some testing when those two arrive. regards, Jogchum -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, It seems that Odroid N2 support is part of upstream kernel and is also in upstream U-Boot. The problem is it requires some binary-only blobs as explained at https://gitlab.denx.de/u-boot/u-boot/-/blob/master/board/amlogic/w400/README... So, not sure how we could package it properly on OBS to create a proper image. Cheers, Guillaume
-----Original Message----- From: Jogchum Reitsma <j.reitsma@hccnet.nl> Sent: 05 April 2020 16:59 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] Support for Hardkernel Odroid N2
Hi,
Are there any plans/is there any progress of enabling opensuse TW or Leap for the Hardkernel Odroid N2? I can't find anything on this list about that, and the last message about this I've seen is on the forum, https://forums.opensuse.org/showthread.php/536160-Initial-success-running- Leap-on-an-ODROID-N2
The last post on that thread is almost a year ago (May 28, 2019)
I've two of them now, both running Ubuntu, and ordered two more at Hardkernel; could take a while before they arrive.
But I could do some testing when those two arrive.
regards, Jogchum
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. N�����r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�����Ǩ�
Not for the first time, I managed to send my answer not to the list.... Apologies! Below my response on Guillaume Op 06-04-2020 om 11:16 schreef Guillaume Gardet:
Hi,
It seems that Odroid N2 support is part of upstream kernel and is also in upstream U-Boot. The problem is it requires some binary-only blobs as explained at https://gitlab.denx.de/u-boot/u-boot/-/blob/master/board/amlogic/w400/README...
So, not sure how we could package it properly on OBS to create a proper image.
Cheers, Guillaume
I don't know enough from packaging (in fact I know nothing about that...) to understand why the necessity to incorporate binary blobs prohibits packaging here, but of course I'll take your word for that. Any chance the situation changes in the near future? But, IIUC, this depends on Amlogic providing sources for the firmware and for tools needed to create the bootloader image, so I think you don't have a clue neither. Thanks for your response! cheers, Jogchum -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 4/9/20 1:06 PM, Jogchum Reitsma wrote:
Not for the first time, I managed to send my answer not to the list.... Apologies!
Below my response on Guillaume
Op 06-04-2020 om 11:16 schreef Guillaume Gardet:
Hi,
It seems that Odroid N2 support is part of upstream kernel and is also in upstream U-Boot. The problem is it requires some binary-only blobs as explained at https://gitlab.denx.de/u-boot/u-boot/-/blob/master/board/amlogic/w400/README...
So, not sure how we could package it properly on OBS to create a proper image.
Cheers, Guillaume
I don't know enough from packaging (in fact I know nothing about that...) to understand why the necessity to incorporate binary blobs prohibits packaging here, but of course I'll take your word for that.
Any chance the situation changes in the near future?
The binary blobs would need a license that allows distribution of them. With that I think we can put them into a OBS project. Regards, Matthias
But, IIUC, this depends on Amlogic providing sources for the firmware and for tools needed to create the bootloader image, so I think you don't have a clue neither.
Thanks for your response!
cheers, Jogchum
Op 09-04-2020 om 14:19 schreef Matthias Brugger:
On 4/9/20 1:06 PM, Jogchum Reitsma wrote:
Not for the first time, I managed to send my answer not to the list.... Apologies!
Below my response on Guillaume
Op 06-04-2020 om 11:16 schreef Guillaume Gardet:
Hi,
It seems that Odroid N2 support is part of upstream kernel and is also in upstream U-Boot. The problem is it requires some binary-only blobs as explained at https://gitlab.denx.de/u-boot/u-boot/-/blob/master/board/amlogic/w400/README...
So, not sure how we could package it properly on OBS to create a proper image.
Cheers, Guillaume
I don't know enough from packaging (in fact I know nothing about that...) to understand why the necessity to incorporate binary blobs prohibits packaging here, but of course I'll take your word for that.
Any chance the situation changes in the near future?
The binary blobs would need a license that allows distribution of them. With that I think we can put them into a OBS project.
Regards, Matthias
Ah, yes, now it becomes clear to me. Thanks. Any chance such a license will be given (by Amlogic,, I suppose)? Anything I can do (not, I suppose)? Regards, Jogchum
But, IIUC, this depends on Amlogic providing sources for the firmware and for tools needed to create the bootloader image, so I think you don't have a clue neither.
Thanks for your response!
cheers, Jogchum
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 4/9/20 6:13 PM, Jogchum Reitsma wrote:
Op 09-04-2020 om 14:19 schreef Matthias Brugger:
On 4/9/20 1:06 PM, Jogchum Reitsma wrote:
Not for the first time, I managed to send my answer not to the list.... Apologies!
Below my response on Guillaume
Op 06-04-2020 om 11:16 schreef Guillaume Gardet:
Hi,
It seems that Odroid N2 support is part of upstream kernel and is also in upstream U-Boot. The problem is it requires some binary-only blobs as explained at https://gitlab.denx.de/u-boot/u-boot/-/blob/master/board/amlogic/w400/README...
So, not sure how we could package it properly on OBS to create a proper image.
Cheers, Guillaume
I don't know enough from packaging (in fact I know nothing about that...) to understand why the necessity to incorporate binary blobs prohibits packaging here, but of course I'll take your word for that.
Any chance the situation changes in the near future?
The binary blobs would need a license that allows distribution of them. With that I think we can put them into a OBS project.
Regards, Matthias
Ah, yes, now it becomes clear to me. Thanks.
Any chance such a license will be given (by Amlogic,, I suppose)? 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. Regards, Matthias
Regards, Jogchum
But, IIUC, this depends on Amlogic providing sources for the firmware and for tools needed to create the bootloader image, so I think you don't have a clue neither.
Thanks for your response!
cheers, Jogchum
<snip> >> 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. > > Regards, > Matthias 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? To pose the right questions from Hardkernel. regards, Jogchum <snip> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 4/13/20 12:19 PM, Jogchum Reitsma wrote: > <snip> >>> 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. >> >> Regards, >> Matthias > 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. Regards, Matthias > > To pose the right questions from Hardkernel. > > > regards, Jogchum > > > <snip> > >
Am 13.04.20 um 12:45 schrieb Matthias Brugger: > On 4/13/20 12:19 PM, Jogchum Reitsma wrote: >> <snip> >>>> 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
participants (4)
-
Andreas Färber -
Guillaume Gardet -
Jogchum Reitsma -
Matthias Brugger