From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot support for OrangePI PC
Date: Sun, 20 Dec 2015 13:37:29 +0100 [thread overview]
Message-ID: <20151220133729.10e6021e@free-electrons.com> (raw)
In-Reply-To: <6b87.5675ed98.926d4@xdna.net>
Hello,
On Sat, 19 Dec 2015 23:51:52 -0000, Cam Hutchison wrote:
> I'll be embarking on this in the new year (OrangePi Plus too). I plan is
> to come up with two defconfigs - one for the 3.4 kernel which supports
> the hardware ok but has a lot of code that is not mainlined and has a
> custom build process, and one for mainline which currently has limited
> support for the H3 and Orange Pi (although there is current activity so
> I'll also track the linux-sunxi kernel too).
Note that we already have such a dual defconfig situation with the
Olimex A20 Olinuxino, with olimex_a20_olinuxino_lime_defconfig using
the mainline kernel, and olimex_a20_olinuxino_lime_mali_defconfig using
the 3.4 sunxi kernel. So I guess we can do the same for other platforms
if needed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-20 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 13:22 [Buildroot] buildroot support for OrangePI PC Eelco Chaudron
2015-12-18 22:23 ` Arnout Vandecappelle
2015-12-20 12:32 ` Eelco Chaudron
2015-12-20 12:45 ` Thomas Petazzoni
2015-12-20 18:17 ` Eelco Chaudron
2015-12-20 18:25 ` Eelco Chaudron
2015-12-24 9:15 ` Eelco Chaudron
2015-12-24 10:28 ` Thomas Petazzoni
2015-12-24 10:52 ` Eelco Chaudron
2015-12-24 11:18 ` Thomas Petazzoni
2015-12-27 0:04 ` Cam Hutchison
2015-12-19 23:51 ` Cam Hutchison
2015-12-20 12:37 ` Thomas Petazzoni [this message]
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=20151220133729.10e6021e@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox