From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Igor Skalkin <Igor.Skalkin@opensynergy.com>,
virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org, luiz.dentz@gmail.com,
marcel@holtmann.org, johan.hedberg@gmail.com,
jasowang@redhat.com
Subject: [virtio-dev] Re: [virtio-comment] [PATCH 1/1] RFC: virtio-bt: add virtio BT device specification
Date: Wed, 15 Mar 2023 12:26:16 -0400 [thread overview]
Message-ID: <20230315122415-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87bkkut29y.fsf@redhat.com>
On Wed, Mar 15, 2023 at 05:20:09PM +0100, Cornelia Huck wrote:
> On Wed, Mar 15 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Wed, Mar 15, 2023 at 04:55:59PM +0100, Cornelia Huck wrote:
> >> On Fri, Mar 10 2023, Igor Skalkin <Igor.Skalkin@opensynergy.com> wrote:
> >> > +\subsection{Feature bits}\label{sec:Device Types / BT Device / Feature bits}
> >> > +
> >> > +\begin{description}
> >> > +\item[VIRTIO_BT_F_VND_HCI (0)] Indicates vendor command support.
> >> > +\item[VIRTIO_BT_F_MSFT_EXT (1)] Indicates MSFT vendor support.
> >> > +\item[VIRTIO_BT_F_AOSP_EXT (2)] Indicates AOSP vendor support.
> >> > +\item[VIRTIO_BT_F_CONFIG_V2 (3)] The device uses the second version of the
> >> > +configuration space structure.
> >> > +\end{description}
> >> > +
> >> > +\devicenormative{\subsubsection}{Feature bits}{Device Types / BT Device / Feature bits}
> >> > +
> >> > +The device MUST require the driver to accept the VIRTIO_BT_F_CONFIG_V2 feature
> >> > +bit, i.e. not set FEATURES_OK without it, and use the second version
> >> > +(struct virtio_bt_config_v2) of the configuration layout, because the
> >> > +first one (struct virtio_bt_config) is unaligned, which violates the
> >> > +specification.
> >>
> >> Did we have a device or driver that didn't use v2? I'm not sure we want
> >> to add a feature for that, other than for backwards compatibility.
> >
> > Linux drivers use a different layout, yes.
>
> Oh, indeed.
>
> >
> > I think it should be possible to implement device without
> > VIRTIO_BT_F_CONFIG_V2 if someone wants to be compatible.
>
> So, do we need to downgrade the requirements for this feature to SHOULD?
>
> >
> > And hmm we need to get back to addressing the negotiation mess ...
For devices I would downgrade it to MAY even.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-03-15 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 6:26 [virtio-dev] [PATCH 0/1] Virtio-bt specification draft Igor Skalkin
2023-03-10 6:26 ` [virtio-dev] [PATCH 1/1] RFC: virtio-bt: add virtio BT device specification Igor Skalkin
2023-03-15 15:55 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-03-15 16:08 ` Michael S. Tsirkin
2023-03-15 16:20 ` Cornelia Huck
2023-03-15 16:26 ` Michael S. Tsirkin [this message]
2023-03-21 23:24 ` [virtio-dev] " Enrico Granata
2023-10-06 16:17 ` Igor Skalkin
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=20230315122415-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Igor.Skalkin@opensynergy.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=virtio-comment@lists.oasis-open.org \
--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