Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] raspberrypi3: fix serial console (load pi3-miniuart-bt overlay)
Date: Mon, 19 Sep 2016 23:57:45 +0200	[thread overview]
Message-ID: <20160919235745.17dc849c@gmx.net> (raw)
In-Reply-To: <20160918192343.1cb566fe@free-electrons.com>

Hello Thomas,

On Sun, 18 Sep 2016 19:23:43 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
> 
> On Mon,  2 May 2016 22:25:44 +0200, Peter Seiderer wrote:
> > - 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>
> > ---
> > Changes v1 --> v2:
> >   - use pi3-miniuart-bt instead of pi3-disable-bt
> >   - fix post-image.sh to add overlay lines only once
> >   - add overlay description (and alternative solution) to readme.txt
> > ---
> >  board/raspberrypi/genimage-raspberrypi3.cfg |  1 +
> >  board/raspberrypi/post-image.sh             | 13 +++++++++++++
> >  board/raspberrypi/readme.txt                |  8 +++++++-
> >  configs/raspberrypi3_defconfig              |  3 ++-
> >  4 files changed, 23 insertions(+), 2 deletions(-)
> 
> What I understood from the discussions on your new patch "raspberrypi3:
> fix serial console (add enable_uart=1", this older proposal is actually
> what is preferred. It is a bit more complicated than just passing
> enable_uart=1, but it allows to have the UART *and* run the CPU as its
> normal frequency.
> 
> So, I've applied this patch, and marked the newer one (enable_uart=1)
> as rejected.
> 
> It would be good if you could rebuild the raspberrypi3_defconfig, and
> check that it works for you. While you're at it, it would be useful if

Still works as expected for me, tested with buildroot git d4db4277ffbd1fae478ba748c626eddc7c220e67,
login via serial and login via hdmi/usb-keyboard possible...

> you could look at the bug report
> https://bugs.busybox.net/show_bug.cgi?id=9196 and see if you can
> reproduce the issue and/or help solve the problem.

Will check the systemd case tomorrow...

Regards,
Peter

> 
> Thanks a lot for your contribution!
> 
> Thomas

      reply	other threads:[~2016-09-19 21:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 20:25 [Buildroot] [PATCH v2] raspberrypi3: fix serial console (load pi3-miniuart-bt overlay) Peter Seiderer
2016-05-03  5:58 ` Oscar Gomez Fuente
2016-05-03  6:18   ` Peter Korsgaard
2016-05-03 10:23     ` Martin Bark
2016-05-03 19:02       ` Peter Seiderer
2016-05-09 13:19         ` Martin Bark
2016-05-09 20:51           ` Peter Seiderer
2016-05-09 20:53             ` Thomas Petazzoni
2016-06-09 20:46         ` Thomas Petazzoni
2016-08-11 22:02           ` Peter Seiderer
2016-09-18 17:23 ` Thomas Petazzoni
2016-09-19 21:57   ` Peter Seiderer [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=20160919235745.17dc849c@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