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 1/1] Preliminary support for Raspberry Pi 3 with symlink
Date: Mon, 25 Apr 2016 21:19:36 +0200	[thread overview]
Message-ID: <20160425211936.73f44f62@gmx.net> (raw)
In-Reply-To: <81b71ac5323b1793405c3192b6ac5264@eja.it>

Hello Ubaldo,

(and sorry from dropping you from CC, your e-mail address seems not to
be reachable from gmx.net)

On Mon, 25 Apr 2016 15:06:54 +0100, Ubaldo Porcheddu <ubaldo@eja.it> wrote:

> Hi Peter,
> 
> Il 2016-04-25 13:07 Peter Korsgaard ha scritto:
> >>>>>> "Ubaldo" == Ubaldo Porcheddu <ubaldo@eja.it> writes:
> > 
> >  > Signed-off-by: Ubaldo Porcheddu <ubaldo@eja.it>
> > 
> > Committed after expanding the commit message, thanks.
> > 
> > I've also committed a change to sync the kernel version with what is
> > used for rpi1/2 (E.G. the rpi-4.4.y branch). Care to verify that
> > everything works correctly after that?
> 
> I just tested the new kernel version but it doesn't give me the login 
> prompt, the kernel seems to be booting fine as it can recognize my 
> keyboard but it doesn't accept any input.
> 
 
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...

Regards,
Peter

[1] http://lists.busybox.net/pipermail/buildroot/2016-April/159295.html

> 
> > What about the serial console? The rpi3 afaik uses ttyS0 instead of
> > ttyAMA0 for the (default) serial console. Do we need to adjust
> > cmdline.txt for the rpi?
> > 
> > I see notes about newer rpi-firmware versions fixing up ttyAMA0 -> 
> > ttyS0
> > when running on a rpi3, so perhaps it isn't needed?
> > 
> > https://github.com/RPi-Distro/repo/issues/22
> 
> I don't have a serial console cable to test with at the moment, but I 
> can see from the kernel log on screen a message like:
> 
> console [ttyS0] enabled
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2016-04-25 19:19 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 [this message]
2016-04-25 19:32       ` Peter Korsgaard
2016-04-25 19:55         ` 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=20160425211936.73f44f62@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