From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Trouble bringing up Raspberry Pi
Date: Sun, 20 Dec 2015 22:48:19 +0100 [thread overview]
Message-ID: <20151220224819.2e9d844e@free-electrons.com> (raw)
In-Reply-To: <20151220201235.GA3766@buinea.com>
Dear Steve Morris,
On Sun, 20 Dec 2015 12:12:35 -0800, Steve Morris wrote:
> I retried on a Pi Model B which had a serial adapter already connected.
>
> The major problem appears to be that the USB keyboard is not working
> using the standard build. It is found during boot and displays messages
> when unplugging/pluging. Perhaps I'm expecting too much.
What behavior are you expecting with the USB keyboard ?
If you expect the key presses on your USB keyboard to appear on your
serial console, then indeed this will not work as it wouldn't make any
sense. The USB keyboard presses should appear on tty1 (i.e on the
screen).
> The network only comes up if I put 'ip=dhcp' in cmdline.txt. This may be
> normal behavior.
By default, Buildroot does not configure any network interface. If all
you want is DHCP on one interface, you can set option BR2_SYSTEM_DHCP
to the name of your network interface.
If you need something more complicated, then it's up to you to provide
a rootfs overlay with your own /etc/network/interfaces file.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-20 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 20:11 [Buildroot] Trouble bringing up Raspberry Pi Steve Morris
2015-12-20 9:27 ` Thomas Petazzoni
2015-12-20 13:36 ` Steve Morris
2015-12-20 13:40 ` Thomas Petazzoni
2015-12-20 20:12 ` Steve Morris
2015-12-20 21:48 ` Thomas Petazzoni [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=20151220224819.2e9d844e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.