From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Unknown PCI Bridge
Date: Fri, 5 May 2006 16:28:15 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0605051625140.1447@home.oyster.ru> (raw)
In-Reply-To: <e3e6rh$ici$1@sea.gmane.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 712 bytes --]
On Fri, 5 May 2006, Sven K?hler wrote:
>> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
>> regression found using the current CVS with ACPI...
>
> I think, this answer is fairly useless for the OP.
> So perhaps the OP wanted to ask: how do i tell my Win2k to properly use
> the new PCI device?
>
> I'm especially interested in this question: is qemu's current ACPI PCI
> device so normal, that it would be recognized and properly used by a
> newly installed Win2k?
>
>
> qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
> a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".
>
Wrong device id, should be 0x7113.
--
mailto:malc@pulsesoft.com
[-- Attachment #2: Type: TEXT/PLAIN, Size: 557 bytes --]
Index: hw/acpi.c
===================================================================
RCS file: /cvsroot/qemu/qemu/hw/acpi.c,v
retrieving revision 1.1
diff -u -r1.1 acpi.c
--- hw/acpi.c 3 May 2006 22:02:44 -0000 1.1
+++ hw/acpi.c 5 May 2006 12:25:49 -0000
@@ -234,7 +234,7 @@
pci_conf[0x00] = 0x86;
pci_conf[0x01] = 0x80;
pci_conf[0x02] = 0x13;
- pci_conf[0x03] = 0x70;
+ pci_conf[0x03] = 0x71;
pci_conf[0x08] = 0x00; // revision number
pci_conf[0x09] = 0x00;
pci_conf[0x0a] = 0x80; // other bridge device
next prev parent reply other threads:[~2006-05-05 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 13:41 [Qemu-devel] Unknown PCI Bridge Chris Bagwell
2006-05-04 18:17 ` Fabrice Bellard
2006-05-05 0:39 ` [Qemu-devel] " Sven Köhler
2006-05-05 12:28 ` malc [this message]
2006-05-05 15:45 ` Sven Köhler
2006-05-05 16:34 ` malc
2006-05-05 17:32 ` Sven Köhler
2006-05-05 17:52 ` malc
2006-05-05 3:01 ` Anthony Liguori
2006-05-06 20:52 ` Sven Köhler
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=Pine.LNX.4.64.0605051625140.1447@home.oyster.ru \
--to=malc@pulsesoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).