From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 PATCH 1/1] Odroid XU4: Hardkernel new board support
Date: Sun, 21 Oct 2018 11:03:33 +0200 [thread overview]
Message-ID: <20181021110333.66837e4b@windsurf> (raw)
In-Reply-To: <1518713437-2163-1-git-send-email-pct@crookies.net>
Hello,
On Thu, 15 Feb 2018 17:50:37 +0100, Pierre CROKAERT wrote:
> This patch provides support for the board Odroid XU4
> This version is using a recent 4.14 kernel released by Hardkernel,
> and the current u-boot 2017.05 also from Hardkernel.
> The support was implemented based on comments about Andi's patch (https://patchwork.ozlabs.org/patch/640695/).
>
> Signed-off-by: Pierre CROKAERT <pct@crookies.net>
> ---
> I made all the modifications we discussed.
> I have also changed the kernel branch to use the latest branch maintained by Hardkernel.
> This patch also includes to replacement of boot.cmd by boot.ini.
> I think it is a better start to support the OdroidXU4 board.
I have applied to master, with the following changes:
[Thomas:
- Update DEVELOPERS file
- Update .gitlab-ci.yml file
- Simplify the boot.ini script
- Add missing BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14 option
- Add BR2_PACKAGE_HOST_DOSFSTOOLS and BR2_PACKAGE_HOST_MTOOLS since a
VFAT filesystem is generated
- Keep the default root filesystem size, since it is sufficient.
- Reduce the size of the VFAT filesystem]
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-21 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 11:02 [Buildroot] [PATCH 1/1] Odroid XU4: Hardkernel new board support Pierre CROKAERT
2018-02-14 21:41 ` Thomas Petazzoni
2018-02-15 9:36 ` Pierre Crokaert
2018-02-15 9:51 ` Thomas Petazzoni
2018-02-15 16:50 ` [Buildroot] [V2 PATCH " Pierre CROKAERT
2018-10-21 9:03 ` Thomas Petazzoni [this message]
2018-02-24 17:06 ` [Buildroot] [PATCH " Pierre Crokaert
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=20181021110333.66837e4b@windsurf \
--to=thomas.petazzoni@bootlin.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