Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Hilber <peter.hilber@oss.qualcomm.com>,
	virtio-comment@lists.linux.dev
Cc: Trilok Soni <trilok.soni@oss.qualcomm.com>
Subject: Re: [PATCH] content: Reserve ID 52 for Snapdragon device
Date: Wed, 26 Aug 2026 17:31:54 +0200	[thread overview]
Message-ID: <1982f2c0-9dad-43b2-94ce-31d03d6a36e5@siemens.com> (raw)
In-Reply-To: <20260826115504.1955-1-peter.hilber@oss.qualcomm.com>

On 26.08.26 13:55, Peter Hilber wrote:
> Reserve a device ID for the Snapdragon device.  A Virtio Snapdragon
> device exposes functionality across Snapdragon SoC subsystems through a
> common Virtio-based protocol.
> 

Virtio is supposed to provide generic hardware models, not so much a
channel to expose concrete, physical chip IP over it. This looks very
weird to me.

Also, isn't Snapdragon a protected brand by Qualcomm? Would it even
legally be fine use it in the spec?

> Device ID 51 is already reserved for the Virtio HAB device:
> 
> https://lore.kernel.org/virtio-comment/20260702140939.3535968-1-zeloren@qti.qualcomm.com/
> 

I think I even voted for this, but likely without checking back what
this may become. I was expecting (hoping?) for a generic, portable inter
VM channel using shared memory. I hope HAB can be that as well - besides
enabling some very Qualcomm-specific and unportable pass-through of
accelerators or so.

Does a "Snapdragon device" have any relation to / dependency on HAB, or
is this just the ID collision why it is mentioned here?

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

  reply	other threads:[~2026-08-26 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 11:55 [PATCH] content: Reserve ID 52 for Snapdragon device Peter Hilber
2026-08-26 15:31 ` Jan Kiszka [this message]
2026-08-26 18:44   ` Stefan Hajnoczi
2026-08-27 13:24     ` Jan Kiszka
2026-08-27 14:49       ` Stefan Hajnoczi
2026-08-27 16:17   ` Peter Hilber
2026-08-27 18:51     ` Jan Kiszka

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=1982f2c0-9dad-43b2-94ce-31d03d6a36e5@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=peter.hilber@oss.qualcomm.com \
    --cc=trilok.soni@oss.qualcomm.com \
    --cc=virtio-comment@lists.linux.dev \
    /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