From: Gerd Hoffmann <kraxel@suse.de>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Xen devel list <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: xensource (pci) device id's?
Date: Thu, 01 Feb 2007 16:45:38 +0100 [thread overview]
Message-ID: <45C20B22.9090802@suse.de> (raw)
In-Reply-To: <45C1F970.3060909@suse.de>
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
Gerd Hoffmann wrote:
> Ian Campbell wrote:
>> We now have vendor 5853 officially assigned.
>
> Ok, how device IDs are allocated? I'd like to use them to tag virtual
> devices ...
... like this (see attached patch), handing out numbers 2-6 ...
cheers,
Gerd
[-- Attachment #2: add-pci-ids.diff --]
[-- Type: text/x-patch, Size: 3226 bytes --]
---
linux-2.6-xen-sparse/drivers/xen/fbfront/xenkbd.c | 6 ++++++
tools/ioemu/hw/cirrus_vga.c | 4 ++++
tools/ioemu/hw/ide.c | 4 ++++
tools/ioemu/hw/rtl8139.c | 6 ++++--
4 files changed, 18 insertions(+), 2 deletions(-)
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
@@ -123,7 +123,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 = 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;
input_set_abs_params(ptr, ABS_X, 0, XENFB_WIDTH, 0, 0);
input_set_abs_params(ptr, ABS_Y, 0, XENFB_HEIGHT, 0, 0);
Index: build-64-unstable-13762/tools/ioemu/hw/rtl8139.c
===================================================================
--- build-64-unstable-13762.orig/tools/ioemu/hw/rtl8139.c
+++ build-64-unstable-13762/tools/ioemu/hw/rtl8139.c
@@ -3423,8 +3423,10 @@ void pci_rtl8139_init(PCIBus *bus, NICIn
pci_conf[0x0e] = 0x00; /* header_type */
pci_conf[0x3d] = 1; /* interrupt pin 0 */
pci_conf[0x34] = 0xdc;
- pci_conf[0x2c] = pci_conf[0x00]; // same as Vendor ID
- pci_conf[0x2d] = pci_conf[0x01];
+ pci_conf[0x2c] = 0x53; /* subsystem vendor: XenSource */
+ pci_conf[0x2d] = 0x58;
+ pci_conf[0x2e] = 0x04; /* subsystem device */
+ pci_conf[0x2f] = 0x00;
s = &d->rtl8139;
Index: build-64-unstable-13762/tools/ioemu/hw/cirrus_vga.c
===================================================================
--- build-64-unstable-13762.orig/tools/ioemu/hw/cirrus_vga.c
+++ build-64-unstable-13762/tools/ioemu/hw/cirrus_vga.c
@@ -3340,6 +3340,10 @@ void pci_cirrus_vga_init(PCIBus *bus, Di
pci_conf[0x0a] = PCI_CLASS_SUB_VGA;
pci_conf[0x0b] = PCI_CLASS_BASE_DISPLAY;
pci_conf[0x0e] = PCI_CLASS_HEADERTYPE_00h;
+ pci_conf[0x2c] = 0x53; /* subsystem vendor: XenSource */
+ pci_conf[0x2d] = 0x58;
+ pci_conf[0x2e] = 0x05; /* subsystem device */
+ pci_conf[0x2f] = 0x00;
/* setup VGA */
s = &d->cirrus_vga;
Index: build-64-unstable-13762/tools/ioemu/hw/ide.c
===================================================================
--- build-64-unstable-13762.orig/tools/ioemu/hw/ide.c
+++ build-64-unstable-13762/tools/ioemu/hw/ide.c
@@ -2502,6 +2502,10 @@ void pci_piix3_ide_init(PCIBus *bus, Blo
pci_conf[0x0a] = 0x01; // class_sub = PCI_IDE
pci_conf[0x0b] = 0x01; // class_base = PCI_mass_storage
pci_conf[0x0e] = 0x00; // header_type
+ pci_conf[0x2c] = 0x53; /* subsystem vendor: XenSource */
+ pci_conf[0x2d] = 0x58;
+ pci_conf[0x2e] = 0x06; /* subsystem device */
+ pci_conf[0x2f] = 0x00;
pci_register_io_region((PCIDevice *)d, 4, 0x10,
PCI_ADDRESS_SPACE_IO, bmdma_map);
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-02-01 15:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 13:53 xensource (pci) device id's? Gerd Hoffmann
2007-02-01 13:58 ` Ian Campbell
2007-02-01 14:30 ` Gerd Hoffmann
2007-02-01 15:45 ` Gerd Hoffmann [this message]
2007-02-02 9:26 ` Ian Campbell
2007-02-02 9:47 ` Gerd Hoffmann
2007-02-02 18:25 ` Keir Fraser
2007-02-05 8:48 ` Gerd Hoffmann
2007-02-05 14:20 ` Gerd Hoffmann
2007-02-02 19:03 ` Keir Fraser
2007-02-05 2:29 ` EPS Signature Kaushik Barde
2007-02-05 2:52 ` Ian Pratt
2007-02-10 7:52 ` GDT access from DOM-0 driver Kaushik Barde
2007-02-11 1:33 ` EPS Signature Kaushik Barde
2007-02-11 10:09 ` Keir Fraser
2007-02-11 23:39 ` Kaushik Barde
2007-02-12 0:58 ` Keir Fraser
2007-02-12 2:36 ` Kaushik Barde
2007-02-12 7:43 ` Keir Fraser
2007-02-06 15:43 ` Andrew D. Ball
2007-02-05 8:55 ` xensource (pci) device id's? Gerd Hoffmann
2007-02-01 20:02 ` Zulauf, John
2007-02-01 20:29 ` Ian Campbell
2007-02-01 23:22 ` Keir Fraser
2007-02-02 8:15 ` Gerd Hoffmann
2007-02-01 23:17 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C20B22.9090802@suse.de \
--to=kraxel@suse.de \
--cc=Ian.Campbell@XenSource.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.