[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac2aaa56-deca-8644-2a42-ca8ee8a77883@linux-m68k.org>
Date: Thu, 7 Jan 2021 23:14:22 +1000
From: Greg Ungerer <gerg@...ux-m68k.org>
To: John Ogness <john.ogness@...utronix.de>,
Vineet Gupta <vgupta@...opsys.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>,
Shreyas Joshi <shreyas.joshi@...mp.com>,
shreyasjoshi15@...il.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel@...r.kernel.org, buildroot@...ybox.net,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-arch@...r.kernel.org,
arcml <linux-snps-arc@...ts.infradead.org>
Subject: Re: ARC no console output (was Re: [PATCH 1/2] init/console: Use
ttynull as a fallback when there is no console)
Hi John,
On 7/1/21 7:02 pm, John Ogness wrote:
> On 2021-01-06, Vineet Gupta <vgupta@...opsys.com> wrote:
>> This breaks ARC booting (no output on console).
>
> Could you provide the kernel boot arguments that you use? This series is
> partly about addressing users that have used boot arguments that are
> technically incorrect (even if had worked). Seeing the boot arguments of
> users that are not experiencing problems may help to reveal some of the
> unusual console usages until now.
I can show an example for m68knommu which this change breaks too
(with no console output on boot).
All the ColdFire dev board targets (arch/m68k/configs/m5*) have a
compiled in boot argument which is "root=/dev/mtdblock0". They have no
real mechanism to pass boot arguments from their boot loader, so it is
compiled in.
The default mcf serial driver is the console on these and no
"console=ttyS0" argument was required in the past.
Regards
Greg
Powered by blists - more mailing lists