From: Andreas Schwab <schwab@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: gregkh@linuxfoundation.org, jslaby@suse.com,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] serial/sifive: select SERIAL_EARLYCON
Date: Tue, 10 Sep 2019 16:42:33 +0200 [thread overview]
Message-ID: <mvmftl4p606.fsf@suse.de> (raw)
In-Reply-To: <20190910143630.GA6794@lst.de> (Christoph Hellwig's message of "Tue, 10 Sep 2019 16:36:30 +0200")
On Sep 10 2019, Christoph Hellwig <hch@lst.de> wrote:
> On Tue, Sep 10, 2019 at 10:18:15AM +0200, Andreas Schwab wrote:
>> > How so? Wіth OF and a stdout path you just set earlycon on the
>> > command line without any arguments and it will be found.
>>
>> Doesn't work for me.
>>
>> [ 0.000000] Malformed early option 'earlycon'
>
> That functionality is implemented by param_setup_earlycon and
> early_init_dt_scan_chosen_stdout. Check why those aren't built into
> your kernel.
They are.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-09-10 14:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 5:59 [PATCH] serial/sifive: select SERIAL_EARLYCON Christoph Hellwig
2019-09-10 6:57 ` Andreas Schwab
2019-09-10 7:05 ` Christoph Hellwig
2019-09-10 8:18 ` Andreas Schwab
2019-09-10 14:36 ` Christoph Hellwig
2019-09-10 14:42 ` Andreas Schwab [this message]
2019-09-13 20:40 ` Palmer Dabbelt
2019-09-16 6:42 ` Christoph Hellwig
2019-09-16 16:12 ` Palmer Dabbelt
2019-09-16 19:40 ` Andreas Schwab
2019-09-16 21:38 ` Palmer Dabbelt
2019-09-17 7:43 ` Andreas Schwab
2019-10-04 21:45 ` Atish Patra
2019-09-16 11:57 ` Paul Walmsley
2019-09-16 12:00 ` Andreas Schwab
2019-09-16 12:15 ` Christoph Hellwig
2019-09-16 12:18 ` Paul Walmsley
2019-09-16 12:22 ` Christoph Hellwig
2019-09-16 10:21 ` Paul Walmsley
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=mvmftl4p606.fsf@suse.de \
--to=schwab@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).