public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, amit.shah@qumranet.com
Cc: kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 03/14] QEMU: Fill in PCI subsystem vendor id for e1000
Date: Mon, 26 May 2008 12:36:13 -0600 (MDT)	[thread overview]
Message-ID: <20080526.123613.-1676919979.imp@bsdimp.com> (raw)
In-Reply-To: <1211798213-4187-6-git-send-email-amit.shah@qumranet.com>

Picking a random one to reply to:

In message: <1211798213-4187-6-git-send-email-amit.shah@qumranet.com>
            Amit Shah <amit.shah@qumranet.com> writes:
: The subsystem vendor ID shouldn't be 0x0 or 0xffff according
: to the PCI spec

Old versions of the spec allowed for these values.  Many older PCI
devices have 0xffff as their subvendor ID.  This is especially true
for video cards...

I'd be cautious in applying these patches, since QEMU tends to emulate
very old devices in some cases...

Warner



  parent reply	other threads:[~2008-05-26 18:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 10:36 PCI: Add subsystem vendor IDs and mask writes to RO bits Amit Shah
2008-05-26 10:36 ` [PATCH 01/14] QEMU: Fill in PCI subsystem vendor id for acpi Amit Shah
2008-05-26 10:36   ` [PATCH 1/2] QEMU: Mask writes to RO bits in the status reg of PCI config space Amit Shah
2008-05-26 10:36     ` [PATCH 02/14] QEMU: Fill in PCI subsystem vendor id for cirrus_vga Amit Shah
2008-05-26 10:36       ` [PATCH 2/2] QEMU: Mask writes to RO bits in the command reg of PCI config space Amit Shah
2008-05-26 10:36         ` [PATCH 03/14] QEMU: Fill in PCI subsystem vendor id for e1000 Amit Shah
2008-05-26 10:36           ` [PATCH 04/14] QEMU: Fill in PCI subsystem vendor id for eepro100 Amit Shah
2008-05-26 10:36             ` [PATCH 05/14] QEMU: Fill in PCI subsystem vendor id for ide Amit Shah
2008-05-26 10:36               ` [PATCH 06/14] QEMU: Fill in PCI subsystem vendor id for LSI Amit Shah
2008-05-26 10:36                 ` [PATCH 07/14] QEMU: Fill in PCI subsystem vendor id for ne2000 Amit Shah
2008-05-26 10:36                   ` [PATCH 08/14] QEMU: Fill in PCI subsystem vendor id for pcnet Amit Shah
2008-05-26 10:36                     ` [PATCH 09/14] QEMU: Fill in PCI subsystem vendor id for piix_pci Amit Shah
2008-05-26 10:36                       ` [PATCH 10/14] QEMU: Fill in PCI subsystem vendor id for rtl8139 Amit Shah
2008-05-26 10:36                         ` [PATCH 11/14] QEMU: Fill in PCI subsystem vendor id for usb-ohci Amit Shah
2008-05-26 10:36                           ` [PATCH 12/14] QEMU: Fill in PCI subsystem vendor id for usb-uhci Amit Shah
2008-05-26 10:36                             ` [PATCH 13/14] QEMU: Fill in PCI subsystem vendor id for versatile_pci Amit Shah
2008-05-26 10:36                               ` [PATCH 14/14] QEMU: Fill in PCI subsystem vendor id for vga Amit Shah
2008-05-26 18:36           ` M. Warner Losh [this message]
2008-05-27 15:01             ` [Qemu-devel] [PATCH 03/14] QEMU: Fill in PCI subsystem vendor id for e1000 Amit Shah
2008-05-26 18:33     ` [Qemu-devel] [PATCH 1/2] QEMU: Mask writes to RO bits in the status reg of PCI config space M. Warner Losh

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=20080526.123613.-1676919979.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=amit.shah@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --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