From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M3orv-0001yW-WA for qemu-devel@nongnu.org; Tue, 12 May 2009 06:05:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M3ort-0001w1-2S for qemu-devel@nongnu.org; Tue, 12 May 2009 06:05:49 -0400 Received: from [199.232.76.173] (port=38256 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M3ors-0001vB-JF for qemu-devel@nongnu.org; Tue, 12 May 2009 06:05:48 -0400 Received: from ns1.bonedaddy.net ([70.91.141.202]:44309) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M3oro-0004uc-OB for qemu-devel@nongnu.org; Tue, 12 May 2009 06:05:45 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by ns1.bonedaddy.net (8.14.2/8.14.2) with ESMTP id n4C9qjGM022686 for ; Tue, 12 May 2009 05:52:46 -0400 Subject: Re: [Qemu-devel] usb_linux_update_endp_table: Broken pipe From: Paul Wise In-Reply-To: <1295ed070905120133j4a147071g8f685d5db0903ef2@mail.gmail.com> References: <1242027306.22141.38.camel@chianamo> <1295ed070905120133j4a147071g8f685d5db0903ef2@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4+F4oDeSwkj5fJZeNtZo" Date: Tue, 12 May 2009 18:06:19 +0800 Message-Id: <1242122779.22141.108.camel@chianamo> Mime-Version: 1.0 Reply-To: qemu-devel@nongnu.org, Paul Wise List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel --=-4+F4oDeSwkj5fJZeNtZo Content-Type: text/plain Content-Transfer-Encoding: quoted-printable [Please CC me on any replies, I'm not subscribed] On Tue, 2009-05-12 at 11:33 +0300, Pantelis Koukousoulas wrote: > I think it would be worth to just merge this patch. I asked myself a few = days > ago, but it seems to be a period where qemu moves quite fast (with the mo= ve > to git and all) and there is no time to review usb patches. Seems like it would enable pass-through for a few devices, from Google, USB-serial devices are the most common thing people run into. > Perhaps we should have a usb-specific git tree so that we can test/fix al= l > usb-related patches that are in limbo right now and occasionally propose > merges. Not being a qemu or Linux developer I probably shouldn't comment, but the -staging tree for dumping stuff to be merged seems to work well for Linux so maybe qemu could do the same. > There could be several reasons for that. Note that your device is also a = bit > on the peculiar side, in that it actually has 3 interfaces (and thus 3 dr= ivers). > It could be also a speed/stall problem but this is unlikely since max's w= ork > has made the usb backend reasonably fast these days. Yeah, it is an all-in-one scanner-printer-fax. One of the interfaces is the printer, one the scanner and not sure about the other one. I was using qemu 0.10.3 when I had these issues, how recent is max's work? It actually feels like a speed/stall problem but it really is hard to say. --=20 bye, pabs http://bonedaddy.net/pabs3/ --=-4+F4oDeSwkj5fJZeNtZo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkoJShoACgkQ5Sc9mGvjxCM0ugCfZIP8Tc7HUDObWMUUA9NMlBow lqcAnAsn45wLJrSjipCRc3+/0DADNDYH =tFz2 -----END PGP SIGNATURE----- --=-4+F4oDeSwkj5fJZeNtZo--