From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] orangepi: add basic support for orangepi-one board
Date: Thu, 15 Dec 2016 17:28:04 +0100 [thread overview]
Message-ID: <87wpf1b1ij.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20161213205237.7119-2-geomatsi@gmail.com> (Sergey Matyukevich's message of "Tue, 13 Dec 2016 23:52:37 +0300")
>>>>> "Sergey" == Sergey Matyukevich <geomatsi@gmail.com> writes:
> Board support package includes the following components:
> - mainline u-boot 2016.09.01
> - mainline kernel 4.9
> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
> ---
> board/orangepi/orangepi-one/boot.cmd | 8 +++++++
> board/orangepi/orangepi-one/genimage.cfg | 36 +++++++++++++++++++++++++++++++
> board/orangepi/orangepi-one/post-build.sh | 11 ++++++++++
> board/orangepi/orangepi-one/post-image.sh | 14 ++++++++++++
> board/orangepi/orangepi-one/readme.txt | 29 +++++++++++++++++++++++++
> configs/orangepi_one_defconfig | 29 +++++++++++++++++++++++++
It is a bit annoying that we have to duplicate all files for each of the
several orangepi board variants, so I've added a patch to share the
post-build / post-image scripts and committed both patches, thanks.
> +BR2_TARGET_UBOOT=y
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> +BR2_TARGET_UBOOT_CUSTOM_VERSION=y
> +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2016.09.01"
> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="orangepi_one"
Any specific reason to not use uboot-2016.11?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2016-12-15 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 20:52 [Buildroot] [PATCH 1/2] orangepipc: rename to orangepi-pc Sergey Matyukevich
2016-12-13 20:52 ` [Buildroot] [PATCH 2/2] orangepi: add basic support for orangepi-one board Sergey Matyukevich
2016-12-15 16:28 ` 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=87wpf1b1ij.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