From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Luca <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: PIIX/IDE: ports disabled in PCI config space?
Date: Tue, 05 Jun 2007 16:19:44 +0300 [thread overview]
Message-ID: <466562F0.7020709@qumranet.com> (raw)
In-Reply-To: <68676e00706050609o10d0aa4fw8fbd7c850d0391f2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Luca wrote:
>
> Good point. I'm looking at bochs right now: the BIOS doesn't touch
> that bits. The 2 ports are enabled/disabled - using values from the
> config file - by the reset function of the emulated controller
> (iodev/pci_ide.cc), so they're doing the same thing I've done for
> QEMU.
> I'd rather not touch the BIOS, it's a bit obscure ;-)
No kidding :-)
Maybe if you post your findings to bochs-devel they'd make the change.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-06-05 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 20:51 PIIX/IDE: ports disabled in PCI config space? Luca Tettamanti
[not found] ` <20070604205159.GB18668-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
2007-06-05 11:52 ` Avi Kivity
[not found] ` <46654E86.8010103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-05 13:09 ` Luca
[not found] ` <68676e00706050609o10d0aa4fw8fbd7c850d0391f2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-05 13:19 ` Avi Kivity [this message]
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=466562F0.7020709@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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