From: Igor Skalkin <Igor.Skalkin@opensynergy.com>
To: virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org, luiz.dentz@gmail.com,
mst@redhat.com
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
jasowang@redhat.com, boris.le.labousse@opensynergy.com,
Igor Skalkin <Igor.Skalkin@opensynergy.com>
Subject: [virtio-comment] [PATCH v2 0/1] Virtio-bt specification draft
Date: Thu, 7 Dec 2023 17:37:20 +0100 [thread overview]
Message-ID: <20231207163721.26737-1-Igor.Skalkin@opensynergy.com> (raw)
We have been using virtio bluetooth linux kernel driver and virtio bluetooth
devices for some time now, but it still has no spec.
This is the first attempt to start developing this specification.
v2->v1:
- Few minor fixes.
- Necessary reference links added to the "Normative References".
- Changes in the configuration V2:
- Field "type" had been removed, because Alternate MAC/PHYs (AMP) secondary
controllers had been removed from the Bluetooth Core Specification since
version 5.3. And this field is not used in the current virtio-bt Linux
implementation.
- Approach of the "vendor" field has been completely changed, now it uses
documented manufacturer identifiers and does not force the driver to use
the hard-coded dependencies between non-documented index value and
vendor-specific parameters.
todo:
- The main question - "Do we have devices based on original (version 1)
configuration, or we can simple purge this version 1 configuration?" - still
has no answer(.
- SCO over HCI test still in process, it is not clear do we need to add
separate queue for the out of band data.
Igor Skalkin (1):
RFC: virtio-bt: add virtio BT device specification
conformance.tex | 12 +-
content.tex | 1 +
device-types/bt/description.tex | 158 +++++++++++++++++++++++++
device-types/bt/device-conformance.tex | 7 ++
device-types/bt/driver-conformance.tex | 7 ++
introduction.tex | 15 +++
6 files changed, 196 insertions(+), 4 deletions(-)
create mode 100644 device-types/bt/description.tex
create mode 100644 device-types/bt/device-conformance.tex
create mode 100644 device-types/bt/driver-conformance.tex
--
2.40.1
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next reply other threads:[~2023-12-07 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:37 Igor Skalkin [this message]
2023-12-07 16:37 ` [virtio-comment] [PATCH v2 1/1] RFC: virtio-bt: add virtio BT device specification Igor Skalkin
2024-01-15 15:09 ` Cornelia Huck
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=20231207163721.26737-1-Igor.Skalkin@opensynergy.com \
--to=igor.skalkin@opensynergy.com \
--cc=boris.le.labousse@opensynergy.com \
--cc=jasowang@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mst@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).