From: "H. Peter Anvin" <hpa@zytor.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9)
Date: Fri, 01 Jan 2010 19:02:59 -0800 [thread overview]
Message-ID: <4B3EB763.4030000@zytor.com> (raw)
In-Reply-To: <20091230164946.GA9858@morn.localdomain>
On 12/30/2009 08:49 AM, Kevin O'Connor wrote:
>
> Hi,
>
> SeaBIOS writes debugging info to port 0x0402. Unfortunately, qemu has
> to be recompiled in order to display this info. Will your patch
> enable one to get at the 0x0402 data without recompiling?
>
> -Kevin
>
Incidentally, it's somewhat unusual choice of ports... port 0x80 is the
normal port for BIOSes to display debugging information on.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-01-02 3:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1262123496-12007-1-git-send-email-hpa@linux.intel.com>
[not found] ` <20091230164946.GA9858@morn.localdomain>
2010-01-02 3:01 ` [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9) H. Peter Anvin
2010-01-02 3:02 ` H. Peter Anvin [this message]
2010-01-02 17:53 ` Kevin O'Connor
2010-01-02 18:56 ` H. Peter Anvin
2010-01-03 2:13 ` François Revol
2010-01-04 14:13 ` [Qemu-devel] " Gerd Hoffmann
2010-01-08 16:36 ` [Qemu-devel] " Anthony Liguori
2009-12-03 5:04 H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2009-12-03 3:11 H. Peter Anvin
2009-12-03 4:02 ` malc
2009-11-20 21:33 H. Peter Anvin
2009-11-23 10:52 ` Gerd Hoffmann
2009-11-23 20:11 ` H. Peter Anvin
2009-11-24 23:05 ` H. Peter Anvin
2009-11-25 7:33 ` Alexander Graf
2009-11-25 12:46 ` Gerd Hoffmann
2009-11-25 18:01 ` H. Peter Anvin
2009-11-25 22:21 ` Gerd Hoffmann
2009-11-25 22:26 ` H. Peter Anvin
2009-11-25 22:31 ` H. Peter Anvin
2009-11-25 22:54 ` Gerd Hoffmann
2009-11-26 9:56 ` Markus Armbruster
2009-11-25 22:53 ` 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=4B3EB763.4030000@zytor.com \
--to=hpa@zytor.com \
--cc=qemu-devel@nongnu.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.