From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] raspberrypi, raspberrypi2: add a serial console
Date: Tue, 29 Mar 2016 16:12:36 +0200 [thread overview]
Message-ID: <56FA8D54.2050605@lucaceresoli.net> (raw)
In-Reply-To: <127322ee36893ff22f57884a111b3434@idefix.lespocky.dyndns.org>
Hei hei Alexander,
thanks for your review! See below by replies.
However, when replying to a mail on the mailing list, please reply to
all. This helps involved people to follow the discussion. Typically an
e-mail sent directly is seen sooner that one on a mailing list only.
On 29/03/2016 13:30, Alexander Dahl wrote:
> Hei hei,
>
> Am 2016-03-29 00:08, schrieb Luca Ceresoli:
>> The current Buildroot defconfigs for Raspberry Pi and Raspberry Pi 2
>> instantiate a console on tty1, which appears on HDMI. Add a console on
>> the serial port (ttyAMA0) to be more consistent with other defconfigs
>> and provide a better out-of-the-box experience to users used to have a
>> serial console from Buildroot defconfigs.
>
> I ran in the very problem last week. So +1 for the idea.
>
>> This requires two changes:
>> 1. have two 'console=' entries in the kernel command line;
>> 2. add a new getty process to the generated inittab.
>
> Then why not split up those two changes in two patches? ;-)
Because change 1 alone is almost useless. It just outputs kernel booting
and early init messages on UART, but no console. I see adding a UART
console as a self-contained change, but of course that's only my opinion.
>
>> -BR2_TARGET_GENERIC_GETTY_PORT="tty1"
>> +BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
>
> +1
>
>> diff --git a/package/rpi-firmware/cmdline.txt b/package/rpi-firmware/cmdline.txt
>> index 38aa3782621b..155a54693bff 100644
>> --- a/package/rpi-firmware/cmdline.txt
>> +++ b/package/rpi-firmware/cmdline.txt
>> @@ -1 +1 @@
>> -root=/dev/mmcblk0p2 rootwait
>> +root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200
>
> +1
>
> Not sure about the post build script though, maybe someone with more
> experience in buildroot could comment on that.
That's OK if you don't feel confident enough to give your official
Acked-by or Reviewed-by tag. Still, you can test the patch on a real
board and report back the outcome. If it works, you can add your
Tested-by tag. Otherwise, please report what went wrong. More details on:
http://nightly.buildroot.org/manual.html#_reviewing_and_testing_patches
Cheers,
--
Luca
next prev parent reply other threads:[~2016-03-29 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 22:08 [Buildroot] [PATCH] raspberrypi, raspberrypi2: add a serial console Luca Ceresoli
2016-03-29 11:30 ` Alexander Dahl
2016-03-29 14:12 ` Luca Ceresoli [this message]
2016-03-29 21:04 ` Alexander Dahl
2016-03-29 22:33 ` Arnout Vandecappelle
2016-03-29 20:32 ` Arnout Vandecappelle
2016-03-29 21:56 ` Luca Ceresoli
2016-03-29 22:46 ` Arnout Vandecappelle
2016-03-30 12:04 ` Luca Ceresoli
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=56FA8D54.2050605@lucaceresoli.net \
--to=luca@lucaceresoli.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