[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [PATCH v2 0/1] Virtio-bt specification draft
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]