From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: xensource (pci) device id's?
Date: Fri, 02 Feb 2007 09:26:34 +0000
Message-ID: <1170408394.4294.76.camel@localhost.localdomain>
References: <45C1F0E1.1070204@suse.de>
	<1170338316.4294.25.camel@localhost.localdomain>
	<45C1F970.3060909@suse.de> <45C20B22.9090802@suse.de>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45C20B22.9090802@suse.de>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Xen devel list <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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.