All of lore.kernel.org
 help / color / mirror / Atom feed
From: code@schulzalex.de
To: Ian Jackson <ian.jackson@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] Reservation of PCI device range 0xc200-0xc2ff to XCP-ng Project
Date: Wed, 17 Oct 2018 17:39:16 +0200	[thread overview]
Message-ID: <5bafc451-d420-908e-7adf-e963b8d8f83e@schulzalex.de> (raw)
In-Reply-To: <23495.20959.216555.482910@mariner.uk.xensource.com>

Am 17.10.2018 um 17:14 schrieb Ian Jackson:
> Alexander Schulz - XCP-ng Project Member writes ("[PATCH] Reservation of PCI device range 0xc200-0xc2ff to XCP-ng Project"):
>> We are the XCP-ng project (https://xcp-ng.org) and want to distribute
>> our own PV-Tools (maybe also per windows updates) so we need an extra range.
> Thanks.  I acked your previous message which was sent by private
> email; I think you could have transferred my ack to this repost.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> I just wanted to say that it is a very good thing to come here and
> reserve a number.  We should assign numbers without too much
> quibbling, which is why I have given a summary ack.
>
> IMO this should be committed soon.
>
>> We also registered a PCI-Device:
>>
>> "XCP-ng Project PCI Device for Windows Update" ->
>> https://pci-ids.ucw.cz/read/PC/5853/c200
> You've got your own PCI device *and* a range in the Xen Platform PCI
> Device ?  I confess I don't know why that is necessary.  Perhaps it is
> more obvious to those who understand this all better than I do.
It was recommended by Paul Durrant: 
https://lists.xenproject.org/archives/html/win-pv-devel/2018-10/msg00005.html

"I think it would probably be better if you took a range. It's not in 
writing but I think other things have played with those low numbered 
device ids in the past so probably best to avoid them. Would you be ok 
with the next range of 0x100 above XenClient, i.e. 0xc200-0xc2ff? ...."

> Regards,
> Ian.

Alexander Schulz
XCP-ng Project Member

Maintainer of: XCP-ng Center and XCP-ng PV-Tools


XCP-ng Project
--------------
web: https://xcp-ng.org
Github: https://github.com/xcp-ng
IRC: #xcp-ng on Freenode


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-10-17 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 20:28 [PATCH] Reservation of PCI device range 0xc200-0xc2ff to XCP-ng Project Alexander Schulz - XCP-ng Project Member
2018-10-17  8:00 ` Paul Durrant
2018-10-17 15:14 ` Ian Jackson
2018-10-17 15:39   ` code [this message]
2018-10-17 15:49 ` Wei Liu
2018-10-17 16:15 ` Ian Jackson
2018-10-17 16:33 ` Wei Liu
2018-10-17 16:36   ` code

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=5bafc451-d420-908e-7adf-e963b8d8f83e@schulzalex.de \
    --to=code@schulzalex.de \
    --cc=ian.jackson@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.