From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] configs/qemu_ppc64_e5500: new defconfig
Date: Mon, 2 Apr 2018 00:43:53 +0200 [thread overview]
Message-ID: <20180402004353.778a61d5@windsurf> (raw)
In-Reply-To: <1522612873-3708-1-git-send-email-matthew.weber@rockwellcollins.com>
Hello,
On Sun, 1 Apr 2018 15:01:13 -0500, Matt Weber wrote:
> Adding basic support modeled after the Freescale/NXP T1040RDBD4
> board.
>
> This target is used to support testing of the bootlin e5500
> toolchain.
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> --
> v1 -> v2
> [Thomas P
> - Fixed title
> - Added defconfig to DEVELOPERS
> - Updated linux config to have more clarification on e500
> - Option to set kernel headers default (missed this in orig as
> 4.15 is default)
> - Adjusted linux cfg to support virtio block device and mount
> a ext fs as the rootfs. Also setup config to support a net
> virtio device(assuming this would come up as a bug eventually)
> ---
> DEVELOPERS | 2 ++
> board/qemu/ppc64-e5500/linux.fragment | 10 ++++++++++
> board/qemu/ppc64-e5500/readme.txt | 7 +++++++
> configs/qemu_ppc64_e5500_defconfig | 20 ++++++++++++++++++++
> 4 files changed, 39 insertions(+)
> create mode 100644 board/qemu/ppc64-e5500/linux.fragment
> create mode 100644 board/qemu/ppc64-e5500/readme.txt
> create mode 100644 configs/qemu_ppc64_e5500_defconfig
Applied to master after updating the .gitlab-ci.yml file. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-01 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 20:01 [Buildroot] [PATCH v2] configs/qemu_ppc64_e5500: new defconfig Matt Weber
2018-04-01 22:43 ` 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=20180402004353.778a61d5@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