From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Yoichi Yuasa <yuasa@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH 1/2] MIPS: add 8250/16550 serial early printk driver
Date: Sat, 6 Feb 2010 13:16:22 +0100 [thread overview]
Message-ID: <20100206121622.GA8775@alpha.franken.de> (raw)
In-Reply-To: <20100205232857.eb65967f.yuasa@linux-mips.org>
On Fri, Feb 05, 2010 at 11:28:57PM +0900, Yoichi Yuasa wrote:
> Signed-off-by: Yoichi Yuasa <yuasa@linux-mips.org>
> ---
> arch/mips/Kconfig.debug | 8 ++++
> arch/mips/include/asm/setup.h | 9 ++++
> arch/mips/kernel/Makefile | 1 +
> arch/mips/kernel/early_printk_8250.c | 68 ++++++++++++++++++++++++++++++++++
> 4 files changed, 86 insertions(+), 0 deletions(-)
> create mode 100644 arch/mips/kernel/early_printk_8250.c
>
> diff --git a/arch/mips/Kconfig.debug b/arch/mips/Kconfig.debug
> index 32a010d..f5d739c 100644
> --- a/arch/mips/Kconfig.debug
> +++ b/arch/mips/Kconfig.debug
> @@ -20,6 +20,14 @@ config EARLY_PRINTK
> doesn't cooperate with an X server. You should normally say N here,
> unless you want to debug such a crash.
>
> +config EARLY_PRINTK_8250
> [..]
have you looked at drivers/serial/8250_early.c ? It looks like it
was invented for some sort of early console on 8250 devices...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2010-02-06 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 14:28 [PATCH 1/2] MIPS: add 8250/16550 serial early printk driver Yoichi Yuasa
2010-02-05 14:30 ` [PATCH 2/2] MIPS: Cobalt move to " Yoichi Yuasa
2010-02-06 12:16 ` Thomas Bogendoerfer [this message]
2010-02-07 23:52 ` [PATCH 1/2] MIPS: add " Yoichi Yuasa
2010-02-08 9:58 ` Sergei Shtylyov
2010-02-08 11:54 ` Yoichi Yuasa
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=20100206121622.GA8775@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yuasa@linux-mips.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