All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-doc: Update to use the new way of attaching USB devices
Date: Thu, 04 May 2017 15:47:57 +0200	[thread overview]
Message-ID: <87wp9wbunm.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <b5440248-708b-780c-791c-451cfdadfef4@redhat.com> (Thomas Huth's message of "Thu, 4 May 2017 14:09:16 +0200")

Thomas Huth <thuth@redhat.com> writes:

> On 04.05.2017 13:48, Markus Armbruster wrote:
>> Thomas Huth <thuth@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.
[...]

  reply	other threads:[~2017-05-04 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  8:58 [Qemu-devel] [PATCH] qemu-doc: Update to use the new way of attaching USB devices Thomas Huth
2017-05-04 11:48 ` Markus Armbruster
2017-05-04 12:09   ` Thomas Huth
2017-05-04 13:47     ` Markus Armbruster [this message]
2017-05-04 14:15   ` Gerd Hoffmann

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=87wp9wbunm.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.