[virtio-dev] Virtio device ID allocation

[virtio-dev] Virtio device ID allocation

[Enrico Weigelt, metux IT consult]

Hello folks,


I'd like to allocate some virtio devices IDs:

a) IDs already used by the Linux kernel:

   VIRTIO_ID_FS             = 26
   VIRTIO_ID_PMEM           = 27
   VIRTIO_ID_MAC80211_HWSIM = 29

b) new devices developed by myself:

   VIRTIO_ID_GPIO           = 30
   VIRTIO_ID_LED            = 31

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

c) planned devices: (no IDs chosen yet)

   VIRTIO_CAN
   VIRTIO_I2C
   VIRTIO_REGULATOR


best regards,

--mtx

-- 
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

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

Re: [virtio-dev] Virtio device ID allocation

[Cornelia Huck]

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

Re: [virtio-dev] Virtio device ID allocation

[Michael S. Tsirkin]

On Wed, Dec 02, 2020 at 12:29:41PM +0100, Enrico Weigelt, metux IT consult wrote:
> Hello folks,
> 
> 
> I'd like to allocate some virtio devices IDs:
> 
> a) IDs already used by the Linux kernel:
> 
>    VIRTIO_ID_FS             = 26
>    VIRTIO_ID_PMEM           = 27
>    VIRTIO_ID_MAC80211_HWSIM = 29
> 
> b) new devices developed by myself:
> 
>    VIRTIO_ID_GPIO           = 30
>    VIRTIO_ID_LED            = 31
> 
>    (attached spec for gpio, led is still under development)
> 
> c) planned devices: (no IDs chosen yet)
> 
>    VIRTIO_CAN
>    VIRTIO_I2C
>    VIRTIO_REGULATOR
> 
> 
> best regards,
> 
> --mtx

So the easiest process to follow to reserve IDs is described here:
https://github.com/oasis-tcs/virtio-spec#use-of-github-issues

> -- 
> ---
> Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
> werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
> GPG/PGP-Schlüssel zu.
> ---
> Enrico Weigelt, metux IT consult
> Free software and Linux embedded engineering
> info@metux.net -- +49-151-27565287
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


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