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?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xensource (pci) device id's?
From: Gerd Hoffmann <kraxel@xxxxxxx>
Date: Mon, 05 Feb 2007 09:55:47 +0100
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Delivery-date: Mon, 05 Feb 2007 00:55:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1E93B88.8CCC%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C1E93B88.8CCC%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20060911)
Keir Fraser wrote:
> On 1/2/07 15:45, "Gerd Hoffmann" <kraxel@xxxxxxx> 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;
> 
> Instead of faking out PCI device ids, which is kinda bogus, can you match in
> the X config file based on the string(s) in {kbd,ptr}->{name,phys,uniq}?
> That'd be nicer than pulling random id numbers out of the air.

You can match name, phys, bustype, vendor, product and version.  Thus a
string in phys should work.  "xenbus/" + nodename maybe?

Nevertheless I think some vendor and product id would be nice, usb hid
devices are usually identified using these two, so having something
useful filled in makes things easier ...

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@xxxxxxx>

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