From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Unknown PCI Bridge
Date: Fri, 5 May 2006 21:52:21 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0605052145280.2152@home.oyster.ru> (raw)
In-Reply-To: <e3g281$g7p$1@sea.gmane.org>
On Fri, 5 May 2006, Sven K?hler wrote:
>>> So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
>>> stuff. I don't know, how odd that might seem to some OS.
>>
>> It's irrelevant to any OS that i know of.
>
> ;-)
>
>>> Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
>>> pciid-database.
>>
>> Huh?
>
> # cat /usr/share/misc/pci.ids|grep -i PIIX3
> 7000 82371SB PIIX3 ISA [Natoma/Triton II]
> 7010 82371SB PIIX3 IDE [Natoma/Triton II]
> 7020 82371SB PIIX3 USB [Natoma/Triton II]
> # cat /usr/share/misc/pci.ids|grep -i PIIX4
> 7110 82371AB/EB/MB PIIX4 ISA
> 7111 82371AB/EB/MB PIIX4 IDE
> 7112 82371AB/EB/MB PIIX4 USB
> 7113 82371AB/EB/MB PIIX4 ACPI
>
>
> See? No PIIX3 ACPI device. That's all i tried to say.
Ok.
More to the point, no machines i have in my vicinity has a PCI device
dedicated to the ACPI. QEMU(old chipsets?) needed it to simplify
delivery of SCI (which must support sharing and be level sensetive)
having PCI device simplifies this somewhat (even though i believe QEMU
does it wrong currently)
There is zero functionality in 7113 or whatnot, it is/was simply a
convenience feature.
--
mailto:malc@pulsesoft.com
next prev parent reply other threads:[~2006-05-05 17:51 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
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 [this message]
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.0605052145280.2152@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).