WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xensource (pci) device id's?

On Thu, 2007-02-01 at 16:45 +0100, Gerd Hoffmann wrote:
>         kbd->name = "Xen Virtual Keyboard";
> +       kbd->id.bustype = BUS_PCI;
> +       kbd->id.vendor  = 0x5853; /* XenSource, Inc. */
> +       kbd->id.product = 0x0002;
>         ptr->name = "Xen Virtual Pointer";
> +       ptr->id.bustype = BUS_PCI;
> +       ptr->id.vendor  = 0x5853; /* XenSource, Inc. */
> +       ptr->id.product = 0x0003; 

This isn't strictly true because this isn't really a PCI device. Is
BUS_HOST not more appropriate?

Possibly we could still use our PCI vendor/product IDs since I guess
they are pretty arbitrary with in the BUS_HOST namespace. What does the
input layer do with these values anyway?

Ian.


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