From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2] usb: Un-deprecate -usbdevice (except for -usbdevice audio which gets removed)
Date: Wed, 10 Mar 2021 16:43:49 +0100 [thread overview]
Message-ID: <20210310154349.cfi5wc4t3t5h5ltp@begin> (raw)
In-Reply-To: <YEjmZOoQJv6XRQc3@redhat.com>
Daniel P. Berrangé, le mer. 10 mars 2021 15:31:48 +0000, a ecrit:
> On Wed, Mar 10, 2021 at 04:26:46PM +0100, Paolo Bonzini wrote:
> > On 10/03/21 16:02, Samuel Thibault wrote:
> > > > > When trying to remove the -usbdevice option, there were complaints that
> > > > > "-usbdevice braille" is still a very useful shortcut for some people.
> > > > Pointer? I missed it.
> > >
> > > For instance
> > > https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00693.html
> >
> > In one sentence: "Braille is worth a special case because a subset of our
> > user base (blind people) will use it 100% of the time, plus it is not
> > supported by libvirt and hence virt-manager".
>
> If simplicity of enabling braille support is critical, we could get
> something even simpler than "-usbdevice braille", and just provide
> a bare "-braille" with no args required as a "do the right thing"
> option ?
That was discussed a bit earlier in the thread:
https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00681.html
https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00686.html
https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00687.html
Just like keyboard/mouse, one would still want to specify whether the
braille device is to be connected through usb or serial, so at least
"-braille usb" and "-braille serial".
Note
https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00689.html
Paolo wrote:
> Adding magic to "-device usb-braille" that creates both a
> front-end and a back-end is completely the opposite of sane...
The thing is: creating one without the other does not make sense.
Samuel
next prev parent reply other threads:[~2021-03-10 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:50 [PATCH v2] usb: Un-deprecate -usbdevice (except for -usbdevice audio which gets removed) Thomas Huth
2021-03-09 17:16 ` Daniel P. Berrangé
2021-03-09 17:21 ` Paolo Bonzini
2021-03-10 12:14 ` Gerd Hoffmann
2021-03-10 10:02 ` Gerd Hoffmann
2021-03-10 10:06 ` Thomas Huth
2021-03-10 13:17 ` Markus Armbruster
2021-03-10 15:02 ` Samuel Thibault
2021-03-10 15:26 ` Paolo Bonzini
2021-03-10 15:31 ` Daniel P. Berrangé
2021-03-10 15:43 ` Samuel Thibault [this message]
2021-03-10 15:44 ` Paolo Bonzini
2021-03-10 16:06 ` Thomas Huth
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=20210310154349.cfi5wc4t3t5h5ltp@begin \
--to=samuel.thibault@gnu.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).