[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] PCI subsystem ids



On 20/8/08 18:04, "Frank van der Linden" <Frank.Vanderlinden@xxxxxxx> wrote:

> But, this isn't done across the board (e.g. the PIIX bridge devices
> don't have these IDs). This makes the Microsoft HCT fail.
> 
> Attached is a patch that makes pci_register_device initialize these
> values with the 0x5853/0x0001 defaults, and removes the explicit inits
> of these values in the various devices.
> 
> A few issues that are worthy of discussion: since Windows use the
> subsystem IDs in its device tree, Windows systems will come up with
> 'found new hardware' after this patch. But, they will just reload the
> same driver, of course, and live happily ever after. Also, we considered
> using Sun PCI subsystem IDs (as we do on our actual hardware), but
> figured that it would be better to use the XenSource ids, so that all
> Xen-based products out there can use eachothers virtual machines with
> minimal hassle.

This should be a patch against the qemu-xen-unstable.git repository. This
would only possibly get applied on the 3.4 branch and we will be deleting
the old qemu tree from the Xen repository very soon when that branch opens.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.