From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] board: added support for Raspberry Pi Zero W
Date: Wed, 21 Jun 2017 22:46:48 +0200 [thread overview]
Message-ID: <20170621224648.44373a00@windsurf> (raw)
In-Reply-To: <1498077584-19344-1-git-send-email-yves.deweerdt.linux@gmail.com>
Hello,
On Wed, 21 Jun 2017 22:39:44 +0200, Yves Deweerdt wrote:
> added a new config file for the Raspberry Pi Zero W (rpi0w)
> - added new folder for raspberrypi0w
> - included the overlays in the genimage config
> - add pi3-miniuart-bt overlay to the config
> - remove rpi0w device tree from the raspberrypi0_defconfig and genimage
>
> Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>
I'd like a review/ack from Peter Seiderer, or other RPi folks of the
Buildroot community. I think the commit log should summarize why the
Zero W support is removed from raspberrypi0_defconfig, and why a
separate defconfig is needed.
> ---
> board/raspberrypi/genimage-raspberrypi0.cfg | 1 -
> board/raspberrypi/genimage-raspberrypi0w.cfg | 31 +++++++++++++++++++++++++
> board/raspberrypi0w | 1 +
> configs/raspberrypi0_defconfig | 2 +-
> configs/raspberrypi0w_defconfig | 34 ++++++++++++++++++++++++++++
> 5 files changed, 67 insertions(+), 2 deletions(-)
> create mode 100644 board/raspberrypi/genimage-raspberrypi0w.cfg
> create mode 120000 board/raspberrypi0w
> create mode 100644 configs/raspberrypi0w_defconfig
An update to board/raspberrypi/readme.txt would be needed.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-21 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 20:39 [Buildroot] [PATCH v2] board: added support for Raspberry Pi Zero W Yves Deweerdt
2017-06-21 20:46 ` Thomas Petazzoni [this message]
2017-06-21 21:09 ` Arnout Vandecappelle
2017-06-22 20:29 ` Peter Seiderer
2018-03-31 10:34 ` Arnout Vandecappelle
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=20170621224648.44373a00@windsurf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.