qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: David Fries <david@fries.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] usb descriptor parsing, why bother?
Date: Mon, 14 May 2012 09:30:47 +0200	[thread overview]
Message-ID: <4FB0B4A7.8000802@redhat.com> (raw)
In-Reply-To: <20120512013246.GP3011@spacedout.fries.net>

On 05/12/12 03:32, David Fries wrote:
> I was bit in kvm-qemu (Debian qemu-kvm-1.0+dfsg-11) with the usb
> descriptor parsing code.  I was enhancing a driver in the guest and
> found that I could talk to usb alt 0, but not alt 3, I made a local
> fix and I see there is an upstream fix (listed below) in qemu.
> 
> commit 96dd9aac37d30f3425088f81523942e67b2d03ac
> Author: Gerd Hoffmann <kraxel@redhat.com>
> Date:   Thu Mar 29 16:06:28 2012 +0200
> usb-host: rewrite usb_linux_update_endp_table

Yea, that one should fix it ;)

> I'm curious why qemu/qemu-kvm even bothers?  As far as I could tell
> parsing the descriptor table is only used to deny the guest from
> submitting urbs on the wrong pipe.

No.  It uses the wMaxPacketSize to pick a useful buffer size for iso
endpoints.  In master / upcoming 1.1 usb-host enables pipelining for
bulk endpoints.

Beside that enabling the usb_host_parse_* tracepoints gives a useful
trace of guest activities (you should see your guest picking alt #3).

cheers,
  Gerd

      reply	other threads:[~2012-05-14  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  1:32 [Qemu-devel] usb descriptor parsing, why bother? David Fries
2012-05-14  7:30 ` Gerd Hoffmann [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=4FB0B4A7.8000802@redhat.com \
    --to=kraxel@redhat.com \
    --cc=david@fries.net \
    --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).