From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Preliminary support for Raspberry Pi 3 with symlink
Date: Mon, 25 Apr 2016 21:55:55 +0200 [thread overview]
Message-ID: <20160425215555.49b860b7@gmx.net> (raw)
In-Reply-To: <87lh41o56p.fsf@dell.be.48ers.dk>
Hello Peter,
On Mon, 25 Apr 2016 21:32:14 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
>
> Hi,
>
> > Same here on RPi3, but with the suggested fix from Oscar Gomez Fuente
> > [1], adding 'dtoverlay=pi3-disable-bt' to config.txt I get working
> > boot messages and login on HDMI and serial console...
>
> Just to confirm, neither serial or HDMI works without the dtoverlay
> line?
Without the overlay I get boot messages on HDMI, but no login, last messages
are from USB keyboard/mouse and I can get more messages removing/adding
keyboard/mouse...., no messages on serial console (but 'ttyS0: 29 input overrun(s)
message on HDMI output)
From linux-3de232825c9ba5989522b8691eb6ac5df6619458/arch/arm/boot/dts/overlays/pi3-disable-bt-overlay.dts:
Disable Bluetooth and restore UART0/ttyAMA0 over GPIOs 14 & 15.
So I think the overlay changes the pin muxing (and the orignal config seems to break
the console, maybe flow control deadlock with the bluetooth chip?)...
>
> I see various references to a clocking issue with the "new" serial port,
> perhaps that is related?
>
This was with old kernel/firmware but adding 'core_freq=250' to config.txt
fixed it...
Regads,
Peter
prev parent reply other threads:[~2016-04-25 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 20:12 [Buildroot] [PATCH 1/1] Preliminary support for Raspberry Pi 3 with symlink Ubaldo Porcheddu
2016-04-25 12:07 ` Peter Korsgaard
2016-04-25 14:06 ` Ubaldo Porcheddu
2016-04-25 14:14 ` Peter Korsgaard
2016-04-25 14:22 ` Ubaldo Porcheddu
2016-04-25 19:07 ` Peter Korsgaard
2016-04-25 14:16 ` Benoît Allard
2016-04-25 14:34 ` Ubaldo Porcheddu
2016-04-25 14:40 ` Peter Korsgaard
2016-04-25 15:10 ` Ubaldo Porcheddu
2016-04-26 14:22 ` Luca Ceresoli
2016-04-25 19:19 ` Peter Seiderer
2016-04-25 19:32 ` Peter Korsgaard
2016-04-25 19:55 ` 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=20160425215555.49b860b7@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