Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] board: add support for nexbox a95x
Date: Sun, 19 Feb 2017 23:23:15 +0100	[thread overview]
Message-ID: <874lzprfak.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170217163310.6929-1-peter@korsgaard.com> (Peter Korsgaard's message of "Fri, 17 Feb 2017 17:33:10 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Nexbox A95X is a low cost Android STB based around an Amlogic s905(x) SoC
 > (quad A53), 8/16GB eMMC and 1/2GB RAM.

 > Both the s905 (gxbb) and s905x (gxl) variant is supported.

 > This defconfig uses mainline Linux.  As the mainline support for s905 is
 > quite young, use the latest release candidate.  There is currently no
 > support for this board in U-Boot or sources available for the vendor U-Boot,
 > so the defconfig doesn't build a u-boot and instead uses the existing U-Boot
 > available in the eMMC.  This also means that we need to wrap the kernel as
 > uImage, which isn't suppported for aarch64.  Instead this is done in the
 > post-build script.

 > Mainline aarch64 defconfig builds most drivers modular, so add mdev for
 > module autoloading.

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to next after explicitly setting BR2_cortex_a53=y in the
defconfig.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2017-02-19 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 16:33 [Buildroot] [PATCH next] board: add support for nexbox a95x Peter Korsgaard
2017-02-19 22:23 ` Peter Korsgaard [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=874lzprfak.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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