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: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xensource (pci) device id's?
From: Gerd Hoffmann <kraxel@xxxxxxx>
Date: Fri, 02 Feb 2007 10:47:17 +0100
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 02 Feb 2007 01:46:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1170408394.4294.76.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <45C1F0E1.1070204@xxxxxxx> <1170338316.4294.25.camel@xxxxxxxxxxxxxxxxxxxxx> <45C1F970.3060909@xxxxxxx> <45C20B22.9090802@xxxxxxx> <1170408394.4294.76.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20060911)
Ian Campbell wrote:
> 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?

Reason I've picked PCI is simply because they are taken from PCI namespace.

> 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?

Nothing.  It's for userspace, to make detection and configuration
easier.  In practice it probably doesn't matter much whenever it is
BUS_PCI or BUS_HOST.  But we should stick with the one we pick ...

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@xxxxxxx>

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