From: Andi Kleen <ak@suse.de>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] early printk for x86
Date: Fri, 15 Nov 2002 04:43:00 +0100 [thread overview]
Message-ID: <20021115044300.C20764@wotan.suse.de> (raw)
In-Reply-To: <3DD428C3.4030700@us.ibm.com>
On Thu, Nov 14, 2002 at 02:50:43PM -0800, Dave Hansen wrote:
> Jeff Garzik wrote:
> >VGA and serial are certainly not hammer+ia32-specific. Make the generic
> >parts generic... the arch-specific components would need to change
> >early-foo base addresses perhaps, but otherwise, it's pretty generic.
>
> Take 2.
>
> - Move the x86_64 early_printk.c into kernel/
> - move some of the basic defines into linux/early_printk.h and
> asm-{i386,x86_64}/early_printk.h
> - run the setup in start_kernel() before setup_arch()
That's overkill. Most architectures have an early_printk equivalent in
firmware. Only i386 and x86-64 are not lucky enough to have one
that is usable from the CPU mode linux uses.
-Andi
next prev parent reply other threads:[~2002-11-15 3:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 19:42 [PATCH] early printk for x86 Dave Hansen
2002-11-14 19:55 ` Andi Kleen
2002-11-14 20:27 ` Jeff Garzik
2002-11-14 22:50 ` Dave Hansen
2002-11-15 3:43 ` Andi Kleen [this message]
2002-11-15 3:52 ` William Lee Irwin III
2002-11-15 4:15 ` H. Peter Anvin
2002-11-14 21:05 ` Jeff Garzik
2002-11-14 23:17 ` Jeff Garzik
2002-11-18 15:15 ` David Woodhouse
2002-11-18 15:17 ` Andi Kleen
2002-11-18 15:39 ` David Woodhouse
[not found] <3DD3FCB3.40506@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <3DD40719.5030108@pobox.com.suse.lists.linux.kernel>
[not found] ` <3DD428C3.4030700@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <20021115044300.C20764@wotan.suse.de.suse.lists.linux.kernel>
[not found] ` <ar1sdm$gfe$1@cesium.transmeta.com.suse.lists.linux.kernel>
2002-11-15 4:31 ` Andi Kleen
2002-11-15 4:33 ` H. Peter Anvin
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=20021115044300.C20764@wotan.suse.de \
--to=ak@suse.de \
--cc=haveblue@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 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.