Thomas Huth <th...@redhat.com> writes:
> On 04.05.2017 13:48, Markus Armbruster wrote:
>> Thomas Huth <th...@redhat.com> writes:
[...]
>>> For instance, user-mode networking can be used with
>>> @example
>>> -qemu-system-i386 [...OPTIONS...] -net user,vlan=0 -usbdevice net:vlan=0
>>> -@end example
>>> -Currently this cannot be used in machines that support PCI NICs.
>>> -@item bt[:@var{hci-type}]
>>> -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{qemu-system-i386} [...@var{OPTIONS}...] @option{-usbdevice}
>>> bt:hci,vlan=3 @option{-bt} device:keyboard,vlan=3
>>> +qemu-system-i386 [...OPTIONS...] -netdev user,id=id0 -device
>>> usb-net,netdev=id0
>>
>> Suggest to use net0 instead of id0 here.
>
> Ok.
>
>>> @end example
>>> +@item usb-bt-dongle
>>> +Bluetooth dongle which implements the USB Transport Layer of HCI.
>>> +It is connected to HCI scatternet 0 by default (corresponds to
>>> +@code{-bt hci,vlan=0}).
>>
>> The Bluetooth documentation you replace is confusing. Ignorant
>> question: is -device ... as expressive as -usbdevice bt:...?
>
> I don't really have a clue about bluetooth in QEMU, too, but from what
> I've seen so far, it does not sound as expressive as the old syntax.
In that case, deprecating -usbdevice bt:... is problematic. However, we
could bring down the big "qdevify or else" hammer: deprecate the
non-qdevified Bluetooth devices with intent to drop unless someone steps
up and does the work they need.
>> docs/qdev-device-use.txt needs an update for this one.
>
> Ok.
[...]
