From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen devel list <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: xensource (pci) device id's?
Date: Mon, 05 Feb 2007 09:48:37 +0100 [thread overview]
Message-ID: <45C6EF65.7000101@suse.de> (raw)
In-Reply-To: <C1E93291.8CBD%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
>
>
> On 1/2/07 15:45, "Gerd Hoffmann" <kraxel@suse.de> wrote:
>
>>> 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 ...
>
> Looks okay. The subvendor device id's can all be the same (e.g., 0x1, as I'm
> not sure about validity of 0x0)
> Sound reasonable?
Yes, 0x01 should be ok, 0x00 isn't valid as far I know.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-02-05 8:48 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
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 [this message]
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=45C6EF65.7000101@suse.de \
--to=kraxel@suse.de \
--cc=Ian.Campbell@XenSource.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.