From: tony.luck@gmail.com (Tony Luck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/7] tty/serial: convert 8250 to generic earlycon
Date: Mon, 9 Jun 2014 15:25:37 -0700 [thread overview]
Message-ID: <CA+8MBb+7f1bOnJjJWj1vxa0UNuQwz7OGRDR_QFTxOT=9cynabQ@mail.gmail.com> (raw)
In-Reply-To: <20140503221658.GA13403@kroah.com>
On Sat, May 3, 2014 at 3:16 PM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>> > >> drivers/tty/serial/8250/8250_early.c | 138 ++++-------------------------------
>> > >> drivers/tty/serial/8250/Kconfig | 1 +
>> > >> 2 files changed, 16 insertions(+), 123 deletions(-)
>> > >
>> > > Hi Greg, Rob
>> > >
>> > > This one in tty-next breaks booting: "console=uart8250,io,0x3f8,115200".
>> > > No early console and regular console anymore.
>> > >
>> > > It should produce "early con and regular con".
>> >
>> > This is what I get for running checkpatch and converting
>> > simple_strtoul to kstrto* which are not so equivalent. kstrto* will
>> > not convert things such as 115200n8 to a number.
>> >
>> > Greg, Do you want a fix or for me to respin the series? The fix looks like this:
>>
>> As this is in my tree now (right?), I need a fix to apply to it.
>
> Nevermind, you already sent it...
Linus' tree (HEAD=963649d735c8) is spitting out all sorts of garbage
on the serial console - as if the baud rate is being periodically set
to something weird, and then back to 112500. I see over a dozen
blocks of junk interspersed with good output.
This in on ia64 with "console=uart,io,0x3f8" on the command line.
git bisect pointed me here:
d2fd6810a823bcde1ee232668f5689837aafa772 is first bad commit
commit d2fd6810a823bcde1ee232668f5689837aafa772
Author: Rob Herring <robh@kernel.org>
Date: Fri Apr 18 17:19:56 2014 -0500
tty/serial: convert 8250 to generic earlycon
-Tony
next prev parent reply other threads:[~2014-06-09 22:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 22:19 [PATCH v2 0/7] Generic serial earlycon Rob Herring
2014-04-18 22:19 ` [PATCH v2 1/7] x86: move FIX_EARLYCON_MEM kconfig into x86 Rob Herring
2014-04-18 22:19 ` [PATCH v2 2/7] tty/serial: add generic serial earlycon Rob Herring
2014-04-18 22:19 ` [PATCH v2 3/7] tty/serial: convert 8250 to generic earlycon Rob Herring
2014-04-26 6:19 ` Yinghai Lu
2014-04-28 23:20 ` Rob Herring
2014-05-03 22:07 ` Greg Kroah-Hartman
2014-05-03 22:16 ` Greg Kroah-Hartman
2014-06-09 22:25 ` Tony Luck [this message]
2014-06-09 22:35 ` Tony Luck
2014-06-09 23:18 ` Rob Herring
2014-06-10 20:52 ` Tony Luck
2014-06-10 22:38 ` Rob Herring
2014-06-11 17:58 ` Rob Herring
2014-06-11 22:20 ` Tony Luck
2014-06-11 23:44 ` Yinghai Lu
2014-06-09 22:36 ` Rob Herring
2014-04-26 6:29 ` Yinghai Lu
2014-04-28 23:24 ` Rob Herring
2014-04-29 2:56 ` Yinghai Lu
2014-04-29 15:16 ` Rob Herring
2014-04-29 18:22 ` Yinghai Lu
2014-04-29 20:41 ` Rob Herring
2014-04-29 22:00 ` Yinghai Lu
2014-04-18 22:19 ` [PATCH v2 4/7] tty/serial: pl011: add generic earlycon support Rob Herring
2014-04-18 22:19 ` [PATCH v2 5/7] tty/serial: add arm/arm64 semihosting earlycon Rob Herring
2014-04-18 22:19 ` [PATCH v2 6/7] arm64: enable FIX_EARLYCON_MEM kconfig Rob Herring
2014-04-18 22:20 ` [PATCH v2 7/7] arm64: remove arch specific earlyprintk Rob Herring
2014-04-29 11:09 ` [PATCH v2 0/7] Generic serial earlycon Catalin Marinas
2014-04-29 15:12 ` Rob Herring
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='CA+8MBb+7f1bOnJjJWj1vxa0UNuQwz7OGRDR_QFTxOT=9cynabQ@mail.gmail.com' \
--to=tony.luck@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).