Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Virtio device ID allocation
Date: Wed, 2 Dec 2020 12:52:49 +0100	[thread overview]
Message-ID: <20201202125249.00be36e6.cohuck@redhat.com> (raw)
In-Reply-To: <91df7aad-02fc-13ca-4592-0b1bc131c7e4@metux.net>

On Wed, 2 Dec 2020 12:29:41 +0100
"Enrico Weigelt, metux IT consult" <lkml@metux.net> wrote:

> Hello folks,
> 
> 
> I'd like to allocate some virtio devices IDs:

The general procedure would be to send a patch to the virtio-comments
list, open an issue, and then request a vote. See
https://github.com/oasis-tcs/virtio-spec#providing-feedback

> 
> a) IDs already used by the Linux kernel:
> 
>    VIRTIO_ID_FS             = 26
>    VIRTIO_ID_PMEM           = 27
>    VIRTIO_ID_MAC80211_HWSIM = 29

These are already in the git tree (even though not yet in an official
version).

> 
> b) new devices developed by myself:
> 
>    VIRTIO_ID_GPIO           = 30
>    VIRTIO_ID_LED            = 31

These two are already reserved for video {en|de}coder devices; you'll
need to bump the numbers beyond 35.

> 
>    (attached spec for gpio, led is still under development)

I don't think attachments will work on this list -- maybe post it as a
separate patch?

> 
> c) planned devices: (no IDs chosen yet)
> 
>    VIRTIO_CAN
>    VIRTIO_I2C

I2C has already been reserved (34); there's also discussion happening
about the proposed spec.

>    VIRTIO_REGULATOR
> 
> 
> best regards,
> 
> --mtx
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2020-12-02 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 11:29 [virtio-dev] Virtio device ID allocation Enrico Weigelt, metux IT consult
2020-12-02 11:52 ` Cornelia Huck [this message]
2020-12-05 19:50 ` Michael S. Tsirkin

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=20201202125249.00be36e6.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=lkml@metux.net \
    --cc=virtio-dev@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox