From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] rpi0w: added support for Raspberry Pi Zero W
Date: Mon, 19 Jun 2017 22:54:36 +0200 [thread overview]
Message-ID: <20170619225436.58ce3391@gmx.net> (raw)
In-Reply-To: <20170619222753.7655732a@windsurf.home>
Hello Thomas, Yves,
On Mon, 19 Jun 2017 22:27:53 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> 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"
>
And the additional genimage line:
+ "rpi-firmware/overlays",
And the 'enable_uart=1' in the config.txt (Is this really needed? For the Pi3 the
overlay solution is enough).
See [1], [2] and [3] for the old suggestion/discussion...
> 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.
>
Regards,
Peter
[1] http://lists.busybox.net/pipermail/buildroot/2017-March/187206.html
[2] http://lists.busybox.net/pipermail/buildroot/2017-March/187377.html
[3] http://lists.busybox.net/pipermail/buildroot/2017-March/187403.html
> Thanks!
>
> Thomas
next prev parent reply other threads:[~2017-06-19 20:54 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
2017-06-19 20:54 ` Peter Seiderer [this message]
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=20170619225436.58ce3391@gmx.net \
--to=ps.report@gmx.net \
--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.