From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] status of odroidc2's support?
Date: Mon, 4 Dec 2017 09:13:10 +0100 [thread overview]
Message-ID: <20171204091310.5295266f@windsurf.home> (raw)
In-Reply-To: <trinity-8c598823-c6de-4b88-91b4-43ba7c4de257-1512369327653@3c-app-mailcom-bs14>
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
next prev parent reply other threads:[~2017-12-04 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 6:35 [Buildroot] status of odroidc2's support? daggs
2017-12-04 8:13 ` Thomas Petazzoni [this message]
2017-12-04 8:27 ` daggs
2017-12-04 10:24 ` Thomas Petazzoni
2017-12-04 20:33 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171204091310.5295266f@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.