From: Greg Ungerer <gerg@linux-m68k.org>
To: John Ogness <john.ogness@linutronix.de>,
Vineet Gupta <vgupta@synopsys.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: linux-arch@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Shreyas Joshi <shreyas.joshi@biamp.com>,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
buildroot@busybox.net, arcml <linux-snps-arc@lists.infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
shreyasjoshi15@gmail.com, Guenter Roeck <linux@roeck-us.net>
Subject: Re: ARC no console output (was Re: [PATCH 1/2] init/console: Use ttynull as a fallback when there is no console)
Date: Thu, 7 Jan 2021 23:14:22 +1000 [thread overview]
Message-ID: <ac2aaa56-deca-8644-2a42-ca8ee8a77883@linux-m68k.org> (raw)
In-Reply-To: <8735zdm86m.fsf@jogness.linutronix.de>
Hi John,
On 7/1/21 7:02 pm, John Ogness wrote:
> On 2021-01-06, Vineet Gupta <vgupta@synopsys.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
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2021-01-07 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201111135450.11214-1-pmladek@suse.com>
[not found] ` <20201111135450.11214-2-pmladek@suse.com>
2021-01-06 23:36 ` ARC no console output (was Re: [PATCH 1/2] init/console: Use ttynull as a fallback when there is no console) Vineet Gupta
2021-01-07 9:02 ` John Ogness
2021-01-07 13:14 ` Greg Ungerer [this message]
2021-01-07 16:43 ` Vineet Gupta
2021-01-07 17:04 ` Petr Mladek
2021-01-07 17:58 ` Vineet Gupta
2021-01-08 3:48 ` Sergey Senozhatsky
2021-01-08 5:18 ` Vineet Gupta
2021-01-08 9:30 ` Petr Mladek
2021-01-13 22:07 ` Peter Korsgaard
2021-01-07 9:09 ` Richard Weinberger
2021-01-07 12:48 ` Petr Mladek
2021-01-07 15:27 ` [Buildroot] " Yann E. MORIN
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=ac2aaa56-deca-8644-2a42-ca8ee8a77883@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=buildroot@busybox.net \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=shreyas.joshi@biamp.com \
--cc=shreyasjoshi15@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@synopsys.com \
/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