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, Igor Skalkin <Igor.Skalkin@opensynergy.com>
Subject: [virtio-dev] [PATCH 0/1] Virtio-bt specification draft
Date: Fri, 10 Mar 2023 07:26:12 +0100 [thread overview]
Message-ID: <20230310062613.109867-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.
Igor Skalkin (1):
RFC: virtio-bt: add virtio BT device specification
conformance.tex | 12 ++-
content.tex | 1 +
device-types/bt/description.tex | 112 +++++++++++++++++++++++++
device-types/bt/device-conformance.tex | 8 ++
device-types/bt/driver-conformance.tex | 8 ++
5 files changed, 137 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.37.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2023-03-10 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 6:26 Igor Skalkin [this message]
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
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=20230310062613.109867-1-Igor.Skalkin@opensynergy.com \
--to=igor.skalkin@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