From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/7] Add rpi3 b+ support
Date: Mon, 19 Mar 2018 18:14:30 +0100 [thread overview]
Message-ID: <20180319181430.4c264d3d@gmx.net> (raw)
In-Reply-To: <20180316232824.7a41721f@windsurf>
Hello Martin,
On Fri, 16 Mar 2018 23:35:48 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Fri, 16 Mar 2018 21:06:52 +0000, Martin Bark wrote:
>
> > The only reason for this seems to be the use of the pi3-miniuart-bt
> > overlay. Personally i never use this overlay, I set enable_uart=1 in
> > config.txt (the same as raspi-config does). Is there a reason
> > buildroot favours the pi3-miniuart-bt overlay?
>
> I am not familiar with those configuration details of the RPi platform,
> but I remember they have been discussed in the past. Perhaps you can
> check the commit log for some details about them.
>
> Especially this commit log:
>
> commit 1e03cc2290f98fc7434254d2abd9afd504de8360
> Author: Peter Seiderer <ps.report@gmx.net>
> Date: Mon May 2 22:25:44 2016 +0200
>
> raspberrypi3: fix serial console (load pi3-miniuart-bt overlay)
>
> - enable BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS in raspberrypi3_defconfig
> - add copy of rpi-firmware/overlays directory to boot partition in genimage-raspberrypi3.cfg
> - enhance post-image.sh script to add 'dtoverlay=pi3-miniuart-bt' on request
> - add BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" in raspberrypi3_defconfig
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
And the full discussion about the different solutions, see [1]...
I am still in prefer the overlay solutions ;-)
Regards,
Peter
[1] https://patchwork.ozlabs.org/patch/617683/
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2018-03-19 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 18:02 [Buildroot] [PATCH v3 0/7] Add rpi3 b+ support Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 1/7] package/rpi-firmware: bump version Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 2/7] configs/raspberrypi*: bump kernel version Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 3/7] board/raspberrypi: add support for rpi3 b+ Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 4/7] package/rpi-firmware: improve installation of dtb files Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 5/7] package/rpi-bt-firmware: change to LibreELEC github repo Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 6/7] package/rpi-wifi-firmware: " Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 7/7] DEVELOPERS: add myself for rpi packages Martin Bark
2018-03-16 19:41 ` [Buildroot] [PATCH v3 0/7] Add rpi3 b+ support Thomas Petazzoni
2018-03-16 21:06 ` Martin Bark
2018-03-16 22:35 ` Thomas Petazzoni
2018-03-19 17:14 ` Peter Seiderer [this message]
2018-03-19 18:18 ` Martin Bark
2018-03-20 12:52 ` Jens Maus
2018-03-22 19:45 ` Martin Bark
2018-03-18 19:07 ` Yann E. MORIN
2018-03-19 9:38 ` Martin Bark
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=20180319181430.4c264d3d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox