xensource (pci) device id's?

[Gerd Hoffmann <kraxel@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 440 bytes --]

  Hi,

Just found this:

  master-xen root ~# grep -A1 -i xensource /usr/share/pci.ids
  fffd  XenSource, Inc.
          0101  PCI Event Channel Controller
  master-xen root ~#

Is this an official vendor id assignment?  Anyone at xensource hands out
device id's?  I'd like give id's to virtual devices (like in the patch
attached) to make hardware detection and configuration easier ...

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>

[-- Attachment #2: fix-xenkbd-2.diff --]
[-- Type: text/x-patch, Size: 917 bytes --]

---
 linux-2.6-xen-sparse/drivers/xen/fbfront/xenkbd.c |    6 ++++++
 1 file changed, 6 insertions(+)

Index: build-64-unstable-13762/linux-2.6-xen-sparse/drivers/xen/fbfront/xenkbd.c
===================================================================
--- build-64-unstable-13762.orig/linux-2.6-xen-sparse/drivers/xen/fbfront/xenkbd.c
+++ build-64-unstable-13762/linux-2.6-xen-sparse/drivers/xen/fbfront/xenkbd.c
@@ -121,7 +121,13 @@ int __devinit xenkbd_probe(struct xenbus
 		set_bit(i, kbd->keybit);
 
 	kbd->name = "Xen Virtual Keyboard";
+	kbd->id.bustype = BUS_PCI;
+	kbd->id.vendor  = 0xfffd; /* XenSource, Inc. */
+	kbd->id.product = 0x0001;
 	ptr->name = "Xen Virtual Touchscreen";
+	ptr->id.bustype = BUS_PCI;
+	ptr->id.vendor  = 0xfffd; /* XenSource, Inc. */
+	ptr->id.product = 0x0002;
 
 	input_set_abs_params(ptr, ABS_X, 0, XENFB_WIDTH, 0, 0);
 	input_set_abs_params(ptr, ABS_Y, 0, XENFB_HEIGHT, 0, 0);

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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