From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] early printk for x86
Date: 14 Nov 2002 20:15:50 -0800 [thread overview]
Message-ID: <ar1sdm$gfe$1@cesium.transmeta.com> (raw)
In-Reply-To: 20021115044300.C20764@wotan.suse.de
Followup to: <20021115044300.C20764@wotan.suse.de>
By author: Andi Kleen <ak@suse.de>
In newsgroup: linux.dev.kernel
>
> 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.
>
That's a pretty big assumption. I wouldn't hold that to be
necessarily true.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-11-15 4:09 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
2002-11-15 3:52 ` William Lee Irwin III
2002-11-15 4:15 ` H. Peter Anvin [this message]
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='ar1sdm$gfe$1@cesium.transmeta.com' \
--to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox