From: Cornelia Huck <cohuck@redhat.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
Demi Marie Obenour <demiobenour@gmail.com>,
Peter Hilber <peter.hilber@oss.qualcomm.com>,
virtio-comment@lists.linux.dev,
Jan Kiszka <jan.kiszka@siemens.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Trilok Soni <trilok.soni@oss.qualcomm.com>
Subject: Re: [PATCH v2] content: Reserve ID 52 for QPSFI device
Date: Thu, 22 Oct 2026 17:05:24 +0200 [thread overview]
Message-ID: <87h5id3he3.fsf@redhat.com> (raw)
In-Reply-To: <oinsf3ecwsrgxuff2m4q3qsjzfg3quldsqv3wjnlzxqbiyzhrz@m4s7bjwc2fsf>
On Thu, Oct 22 2026, Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> wrote:
> Let's define some standard way for the vendors to declare that this
> device is "Qualcomm", "NXP" or "hobbyist which doesn't own PCI or USB id
> block".
Are we able to use the first <n> bytes of config space for that? I guess
that is the only way that can possibly work for any transport.
Then, maybe something like one or two bytes for a vendor id (including
one for "testing purposes" or so), and the rest to be used in a
vendor-specific way.
next prev parent reply other threads:[~2026-10-22 15:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 18:00 [PATCH v2] content: Reserve ID 52 for QPSFI device Peter Hilber
2026-10-21 19:25 ` Demi Marie Obenour
2026-10-21 19:50 ` Michael S. Tsirkin
2026-10-22 4:35 ` Cornelia Huck
2026-10-22 7:07 ` Demi Marie Obenour
2026-10-22 7:24 ` Michael S. Tsirkin
2026-10-22 8:41 ` Manos Pitsidianakis
2026-10-22 13:19 ` Michael S. Tsirkin
2026-10-22 14:07 ` Dmitry Baryshkov
2026-10-22 15:05 ` Cornelia Huck [this message]
2026-10-22 15:35 ` Parav Pandit
2026-10-22 15:41 ` Michael S. Tsirkin
2026-10-22 15:49 ` Parav Pandit
2026-10-22 16:02 ` Michael S. Tsirkin
2026-10-22 16:20 ` Parav Pandit
2026-10-22 16:29 ` Michael S. Tsirkin
2026-10-22 22:39 ` Peter Hilber
2026-10-22 23:28 ` Michael S. Tsirkin
2026-10-23 3:32 ` Parav Pandit
2026-10-23 5:37 ` Manos Pitsidianakis
2026-10-23 5:40 ` Demi Marie Obenour
2026-10-23 20:56 ` Peter Hilber
2026-10-23 23:47 ` Michael S. Tsirkin
2026-10-26 14:31 ` Cornelia Huck
2026-10-28 14:22 ` Peter Hilber
2026-10-22 15:44 ` Michael S. Tsirkin
2026-10-22 14:50 ` Zelong Ren
2026-10-21 19:41 ` Michael S. Tsirkin
2026-10-22 13:56 ` Dmitry Baryshkov
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=87h5id3he3.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=demiobenour@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jan.kiszka@siemens.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mst@redhat.com \
--cc=peter.hilber@oss.qualcomm.com \
--cc=stefanha@redhat.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