From: Christoph Hellwig <hch@lst.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: gregkh@linuxfoundation.org, Andreas Schwab <schwab@suse.de>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
jslaby@suse.com, linux-riscv@lists.infradead.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] serial/sifive: select SERIAL_EARLYCON
Date: Mon, 16 Sep 2019 14:22:49 +0200 [thread overview]
Message-ID: <20190916122249.GA30058@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1909160513100.9917@viisi.sifive.com>
On Mon, Sep 16, 2019 at 05:18:57AM -0700, Paul Walmsley wrote:
> I support Christoph's plan to add generic implicit earlycon support.
I'm not planning to add it, it exist already. You just need a DT that
sets the stdout node up properly, and a earlycon driver using
OF_EARLYCON_DECLARE like the sifive uart driver.
The DT here for example works perfectly fine:
http://git.infradead.org/users/hch/riscv.git/commitdiff/f10e64873eafc68516b8884c06b9290b9887633b
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Andreas Schwab <schwab@suse.de>, Christoph Hellwig <hch@lst.de>,
gregkh@linuxfoundation.org, jslaby@suse.com,
linux-serial@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial/sifive: select SERIAL_EARLYCON
Date: Mon, 16 Sep 2019 14:22:49 +0200 [thread overview]
Message-ID: <20190916122249.GA30058@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1909160513100.9917@viisi.sifive.com>
On Mon, Sep 16, 2019 at 05:18:57AM -0700, Paul Walmsley wrote:
> I support Christoph's plan to add generic implicit earlycon support.
I'm not planning to add it, it exist already. You just need a DT that
sets the stdout node up properly, and a earlycon driver using
OF_EARLYCON_DECLARE like the sifive uart driver.
The DT here for example works perfectly fine:
http://git.infradead.org/users/hch/riscv.git/commitdiff/f10e64873eafc68516b8884c06b9290b9887633b
next prev parent reply other threads:[~2019-09-16 12:22 UTC|newest]
Thread overview: 41+ 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 5:59 ` Christoph Hellwig
2019-09-10 6:57 ` Andreas Schwab
2019-09-10 6:57 ` Andreas Schwab
2019-09-10 7:05 ` Christoph Hellwig
2019-09-10 7:05 ` Christoph Hellwig
2019-09-10 8:18 ` Andreas Schwab
2019-09-10 8:18 ` Andreas Schwab
2019-09-10 14:36 ` Christoph Hellwig
2019-09-10 14:36 ` Christoph Hellwig
2019-09-10 14:42 ` Andreas Schwab
2019-09-10 14:42 ` Andreas Schwab
2019-09-13 20:40 ` Palmer Dabbelt
2019-09-13 20:40 ` Palmer Dabbelt
2019-09-13 20:40 ` Palmer Dabbelt
2019-09-16 6:42 ` Christoph Hellwig
2019-09-16 6:42 ` Christoph Hellwig
2019-09-16 16:12 ` Palmer Dabbelt
2019-09-16 16:12 ` Palmer Dabbelt
2019-09-16 16:12 ` Palmer Dabbelt
2019-09-16 19:40 ` Andreas Schwab
2019-09-16 19:40 ` Andreas Schwab
2019-09-16 21:38 ` Palmer Dabbelt
2019-09-16 21:38 ` Palmer Dabbelt
2019-09-16 21:38 ` Palmer Dabbelt
2019-09-17 7:43 ` Andreas Schwab
2019-09-17 7:43 ` Andreas Schwab
2019-10-04 21:45 ` Atish Patra
2019-10-04 21:45 ` Atish Patra
2019-09-16 11:57 ` Paul Walmsley
2019-09-16 11:57 ` Paul Walmsley
2019-09-16 12:00 ` Andreas Schwab
2019-09-16 12:00 ` Andreas Schwab
2019-09-16 12:15 ` Christoph Hellwig
2019-09-16 12:15 ` Christoph Hellwig
2019-09-16 12:18 ` Paul Walmsley
2019-09-16 12:18 ` Paul Walmsley
2019-09-16 12:22 ` Christoph Hellwig [this message]
2019-09-16 12:22 ` Christoph Hellwig
2019-09-16 10:21 ` Paul Walmsley
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=20190916122249.GA30058@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=schwab@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.