From: "David S. Ahern" <daahern@cisco.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] usb-host quirks
Date: Tue, 02 Feb 2010 17:36:35 -0700 [thread overview]
Message-ID: <4B68C513.5080205@cisco.com> (raw)
In-Reply-To: <201002021442.07991.mb@bu3sch.de>
On 02/02/2010 06:42 AM, Michael Buesch wrote:
> Hi,
>
> I've got a buggy device that needs a special workaround to be usable under
> host-usb access. The device really doesn't like being reset via USBDEVFS_RESET. It
> immediatenly locks up the device firmware or whatever. It won't respond properly anymore.
> With the following patch it works fine, though.
>
What about the USBDEVFS_RESET in usb_host_open? Does that have an impact?
For some USB keys I have had to add an additional reset prior to
claiming interfaces:
diff --git a/usb-linux.c b/usb-linux.c
index 1aaa595..092e75c 100644
--- a/usb-linux.c
+++ b/usb-linux.c
@@ -906,6 +906,9 @@ static int usb_host_open(USBHostDevice *dev, int
bus_num,
#endif
+ /* some keys require a reset before the getconfig */
+ ioctl(fd, USBDEVFS_RESET);
+
/*
* Initial configuration is -1 which makes us claim first
* available config. We used to start with 1, which does not
David Ahern
> So I was wondering what the accepted way was to get these quirks upstream into the qemu
> source tree. Is usb-linux.c the correct place, or should we put the quirk into
> a different place?
>
> ---
> usb-linux.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> --- qemu.orig/usb-linux.c
> +++ qemu/usb-linux.c
> @@ -389,6 +389,10 @@ static void usb_host_handle_reset(USBDev
>
> dprintf("husb: reset device %u.%u\n", s->bus_num, s->addr);
>
> + if (((s->descr[8] << 8) | s->descr[9]) == 0x2471 &&
> + ((s->descr[10] << 8) | s->descr[11]) == 0x0853)
> + return;
> +
> ioctl(s->fd, USBDEVFS_RESET);
>
> usb_host_claim_interfaces(s, s->configuration);
>
prev parent reply other threads:[~2010-02-03 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 13:42 [Qemu-devel] usb-host quirks Michael Buesch
2010-02-03 0:36 ` David S. Ahern [this message]
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=4B68C513.5080205@cisco.com \
--to=daahern@cisco.com \
--cc=mb@bu3sch.de \
--cc=qemu-devel@nongnu.org \
/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).