Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W
Date: Mon, 19 Jun 2017 22:27:53 +0200	[thread overview]
Message-ID: <20170619222753.7655732a@windsurf.home> (raw)
In-Reply-To: <1497815044-11215-1-git-send-email-yves.deweerdt.linux@gmail.com>

Hello,

On Sun, 18 Jun 2017 21:44:04 +0200, Yves Deweerdt wrote:
> added a new config file for the Raspberry Pi Zero W
> - added new folder for raspberrypi0w
> - included the overlays in the genimage config
> - add pi3-miniuart-bt overlay to the config
> - add enable_uart to the config
> 
> Signed-off-by: Yves Deweerdt <yves.deweerdt.linux@gmail.com>

I am a bit confused: what do you need in this defconfig, that the
existing raspberrypi0_defconfig doesn't provide?

Your proposed defconfig is using the exact same kernel version and list
of Device Trees. The only differences are:

+BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y

and:

+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"

Is this the motivation for this separate defconfig? Could the existing
raspberrypi0_defconfig be extended to also work for your use case,
while keeping compatibility for the RPi Zero ?

If not, we should remove the RPi Zero W support from
raspberrypi0_defconfig, because otherwise things are pretty confusing.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-06-19 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 19:44 [Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W Yves Deweerdt
2017-06-19 20:27 ` Thomas Petazzoni [this message]
2017-06-19 20:54   ` Peter Seiderer
2017-06-20  9:39     ` Yves Deweerdt
2017-06-20 19:19       ` Peter Seiderer
2017-06-21 17:22         ` Yves Deweerdt
2017-06-21 20:35         ` Yves Deweerdt
2017-06-22 20:19           ` Peter Seiderer

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=20170619222753.7655732a@windsurf.home \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox