diff options
author | Thomas Huth <thuth@redhat.com> | 2019-11-20 10:10:12 +0100 |
---|---|---|
committer | Thomas Huth <thuth@redhat.com> | 2019-12-16 17:24:07 +0100 |
commit | 43d68d0a94ef13058f6479b3dd490169a9a62966 (patch) | |
tree | 0d28c09bb13f4af47dbf300233f4dabddb5e157c /qemu-doc.texi | |
parent | 6da68df7f9b92e901263ea065712a289c8d3838e (diff) |
hw/usb: Remove the USB bluetooth dongle device
We are going to remove the bluetooth backend, so the USB bluetooth
dongle can not work anymore. It's a completely optional device, no
board depends on it, so let's simply remove it now.
Message-Id: <20191120091014.16883-3-thuth@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'qemu-doc.texi')
-rw-r--r-- | qemu-doc.texi | 15 |
1 files changed, 0 insertions, 15 deletions
diff --git a/qemu-doc.texi b/qemu-doc.texi index ed3df01dac..eea91a2d1e 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -983,21 +983,6 @@ For instance, user-mode networking can be used with Smartcard reader device @item usb-audio USB audio device -@item usb-bt-dongle -Bluetooth dongle for the transport layer of HCI. It is connected to HCI -scatternet 0 by default (corresponds to @code{-bt hci,vlan=0}). -Note that the syntax for the @code{-device usb-bt-dongle} option is not as -useful yet as it was with the legacy @code{-usbdevice} option. So to -configure an USB bluetooth device, you might need to use -"@code{-usbdevice bt}[:@var{hci-type}]" instead. This configures a -bluetooth dongle whose type is specified in the same format as with -the @option{-bt hci} option, @pxref{bt-hcis,,allowed HCI types}. If -no type is given, the HCI logic corresponds to @code{-bt hci,vlan=0}. -This USB device implements the USB Transport Layer of HCI. Example -usage: -@example -@command{@value{qemu_system}} [...@var{OPTIONS}...] @option{-usbdevice} bt:hci,vlan=3 @option{-bt} device:keyboard,vlan=3 -@end example @end table @node host_usb_devices |