qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Mark Burkley <qemu@emutex.com>,
	qemu-devel@nongnu.org, Max Krasnyansky <maxk@qualcomm.com>
Subject: [Qemu-devel] Re: [PATCH] usb-linux: return USB_RET_STALL on -EPIPE
Date: Tue, 13 Oct 2009 08:46:04 -0500	[thread overview]
Message-ID: <4AD4849C.3000600@us.ibm.com> (raw)
In-Reply-To: <1255434008.1817.40.camel@localhost.localdomain>

Paul Bolle wrote:
> 0) This is an attempt to get an issue in usb-linux.c, for which a patch
> was posted about a year ago, finally fixed.
>
> 1) Mark Burkley submitted a "EHCI emulation module" for review in in
> October 2008 (see:
> http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg01326.html). No
> EHCI emulation module was ever committed to qemu.
>   

Yeah, it's ashame that noone's followed up with this patch.

> 2) Part of that (large) patch was a fix for a separate issue in
> usb-linux.c. Max Krasnyansky has ACK'ed that fix (see:
> http://lists.gnu.org/archive/html/qemu-devel/2008-11/msg00032.html).
>
> 3) I already asked whether this fix was ready to be committed in last
> April (see:
> http://lists.gnu.org/archive/html/qemu-devel/2009-04/msg01763.html)
>
> 4) Maybe submitting this fix as a separate patch (with a really long
> commit message but without a Signed-off-by) and cc-ing everbody involved
> will help if actually getting this issue fixed.
>   

Yes, separate fixes should always be separate patches.

> Ok. I just tested that change (ie returning STALL instead of NAK on EPIPE)
> with a bunch of devices: USB serial adapter, CF card reader, USB webcam (MS
> VX-3000) and MS USB mouse. All that stuff was hooked up to XP-SP3 and all of
> them are perfectly usable at the same time.
>
> In other words here is my ACK :)
>
> Acked-by: Max Krasnyansky <maxk@qualcomm.com>
> Tested-by: Paul Bolle <pebolle@tiscali.nl>
>   

Someone needs to  provide a Signed-off-by.

> ---
>  usb-linux.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/usb-linux.c b/usb-linux.c
> index 9e5d9c4..d712134 100644
> --- a/usb-linux.c
> +++ b/usb-linux.c
> @@ -275,7 +275,9 @@ static void async_complete(void *opaque)
>
>              case -EPIPE:
>                  set_halt(s, p->devep);
> -                /* fall through */
> +		p->len = USB_RET_STALL;
> +		break;
> +
>              default:
>                  p->len = USB_RET_NAK;
>                  break;
>   


-- 
Regards,

Anthony Liguori

  reply	other threads:[~2009-10-13 13:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 11:40 [Qemu-devel] [PATCH] usb-linux: return USB_RET_STALL on -EPIPE Paul Bolle
2009-10-13 13:46 ` Anthony Liguori [this message]
2009-10-13 15:52   ` [Qemu-devel] " Paul Bolle
2009-10-13 16:04     ` Anthony Liguori
2009-10-13 16:12       ` Paul Bolle
2009-10-13 16:22         ` Anthony Liguori
2009-10-13 17:23           ` Max Krasnyansky
2009-10-13 18:53             ` Paul Bolle

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=4AD4849C.3000600@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=maxk@qualcomm.com \
    --cc=pebolle@tiscali.nl \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@emutex.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).