* [Buildroot] status of odroidc2's support? @ 2017-12-04 6:35 daggs 2017-12-04 8:13 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: daggs @ 2017-12-04 6:35 UTC (permalink / raw) To: buildroot Greetings, now that gcc 4.9.x was dropped from buildroot, is it impossible to build the vendor's version of odroidc2. (uboot doesn't compile) so the is no way to build a workable image for this board. I think there support for gcc5 was added but not for gcc6. I've tried to add support for gcc6 but it won't boot the kernel. unfortunately, I don't have any time to handle both vendor and mainline support. I wonder if it worthwhile to continue my support for it. I know that soon to be mainline kernel 4.15 has hdmi support but I don't know for what extent (still trying to figure it out), one thing is sure, there will be no hw decoding support. is there a way to restore support for the vendor's flavor? maybe and external toolchain? Dagg. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] status of odroidc2's support? 2017-12-04 6:35 [Buildroot] status of odroidc2's support? daggs @ 2017-12-04 8:13 ` Thomas Petazzoni 2017-12-04 8:27 ` daggs 0 siblings, 1 reply; 5+ messages in thread From: Thomas Petazzoni @ 2017-12-04 8:13 UTC (permalink / raw) To: buildroot Hello, On Mon, 4 Dec 2017 07:35:27 +0100, daggs wrote: > now that gcc 4.9.x was dropped from buildroot, Gcc 4.9 is not dropped from Buildroot, it's still there in the current Git master. > is it impossible to build the vendor's version of odroidc2. (uboot > doesn't compile) > so the is no way to build a workable image for this board. I think > there support for gcc5 was added but not for gcc6. I've tried to add > support for gcc6 but it won't boot the kernel. > > unfortunately, I don't have any time to handle both vendor and > mainline support. I wonder if it worthwhile to continue my support > for it. I know that soon to be mainline kernel 4.15 has hdmi support > but I don't know for what extent (still trying to figure it out), one > thing is sure, there will be no hw decoding support. is there a way > to restore support for the vendor's flavor? maybe and external > toolchain? Getting U-Boot to build with gcc 5.x should just be a matter of backporting a U-Boot patch. Can you try applying something like ./roseapplepi/patches/uboot/0001-compiler-.h-sync-include-linux-compiler-.h-with-Linu.patch to your U-Boot and see if it works ? Thanks! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] status of odroidc2's support? 2017-12-04 8:13 ` Thomas Petazzoni @ 2017-12-04 8:27 ` daggs 2017-12-04 10:24 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: daggs @ 2017-12-04 8:27 UTC (permalink / raw) To: buildroot Greetings Thomas, > Sent: Monday, December 04, 2017 at 10:13 AM > From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com> > To: daggs <daggs@gmx.com> > Cc: buildroot at buildroot.org > Subject: Re: [Buildroot] status of odroidc2's support? > > Hello, > > On Mon, 4 Dec 2017 07:35:27 +0100, daggs wrote: > > > now that gcc 4.9.x was dropped from buildroot, > > Gcc 4.9 is not dropped from Buildroot, it's still there in the current > Git master. > > > is it impossible to build the vendor's version of odroidc2. (uboot > > doesn't compile) > > so the is no way to build a workable image for this board. I think > > there support for gcc5 was added but not for gcc6. I've tried to add > > support for gcc6 but it won't boot the kernel. > > > > unfortunately, I don't have any time to handle both vendor and > > mainline support. I wonder if it worthwhile to continue my support > > for it. I know that soon to be mainline kernel 4.15 has hdmi support > > but I don't know for what extent (still trying to figure it out), one > > thing is sure, there will be no hw decoding support. is there a way > > to restore support for the vendor's flavor? maybe and external > > toolchain? > > Getting U-Boot to build with gcc 5.x should just be a matter of > backporting a U-Boot patch. Can you try applying something > like ./roseapplepi/patches/uboot/0001-compiler-.h-sync-include-linux-compiler-.h-with-Linu.patch > to your U-Boot and see if it works ? > > Thanks! > > Thomas > -- strange, when running menuconfig, I see only gcc 6 and gcc 7 in the version selection menu. what am I missing? I think the branch already supports gcc5 Dagg. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] status of odroidc2's support? 2017-12-04 8:27 ` daggs @ 2017-12-04 10:24 ` Thomas Petazzoni 2017-12-04 20:33 ` Yann E. MORIN 0 siblings, 1 reply; 5+ messages in thread From: Thomas Petazzoni @ 2017-12-04 10:24 UTC (permalink / raw) To: buildroot Hello, On Mon, 4 Dec 2017 09:27:20 +0100, daggs wrote: > strange, when running menuconfig, I see only gcc 6 and gcc 7 in the version selection menu. what am I missing? > I think the branch already supports gcc5 Meh, it's the recent introduction of Cortex-A35 (commit e9960da6ec84d0fc4f3d7ef8d9db5b1e29d79358 from Yann, added in Cc) that broke this. Due to this commit, Cortex-A35 is now the first AArch64 core, and therefore the one selected by default instead of Cortex-A53. So, a defconfig that has just BR2_aarch64=y will now build for Cortex-A35 instead of Cortex-A53. However, Cortex-A35 support was only added in gcc 6.x, so only gcc 6.x/7.x are allowed. Dagg, you can for now fix that by selecting Cortex-A53 explicitly in your defconfig: BR2_aarch64=y BR2_cortex_a53=y Yann, do you think we should add a "default BR2_cortex_a53 if BR2_aarch64 || BR2_aarch64eb" in the choice ? Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] status of odroidc2's support? 2017-12-04 10:24 ` Thomas Petazzoni @ 2017-12-04 20:33 ` Yann E. MORIN 0 siblings, 0 replies; 5+ messages in thread From: Yann E. MORIN @ 2017-12-04 20:33 UTC (permalink / raw) To: buildroot Thomas, daggs, All, On 2017-12-04 11:24 +0100, Thomas Petazzoni spake thusly: > On Mon, 4 Dec 2017 09:27:20 +0100, daggs wrote: > > strange, when running menuconfig, I see only gcc 6 and gcc 7 in the version selection menu. what am I missing? > > I think the branch already supports gcc5 > > Meh, it's the recent introduction of Cortex-A35 (commit > e9960da6ec84d0fc4f3d7ef8d9db5b1e29d79358 from Yann, added in Cc) that > broke this. > > Due to this commit, Cortex-A35 is now the first AArch64 core, and > therefore the one selected by default instead of Cortex-A53. > > So, a defconfig that has just > > BR2_aarch64=y > > will now build for Cortex-A35 instead of Cortex-A53. However, > Cortex-A35 support was only added in gcc 6.x, so only gcc 6.x/7.x are > allowed. > > Dagg, you can for now fix that by selecting Cortex-A53 explicitly in > your defconfig: > > BR2_aarch64=y > BR2_cortex_a53=y > > Yann, do you think we should add a "default BR2_cortex_a53 if > BR2_aarch64 || BR2_aarch64eb" in the choice ? Yes, adding a better default value makes sense. The re-organisation was so that the list gets sorted. It is not an endosement of a better default. I'll send a patch. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-12-04 20:33 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2017-12-04 6:35 [Buildroot] status of odroidc2's support? daggs 2017-12-04 8:13 ` Thomas Petazzoni 2017-12-04 8:27 ` daggs 2017-12-04 10:24 ` Thomas Petazzoni 2017-12-04 20:33 ` Yann E. MORIN
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.