From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Np3Vm-0003hi-G6 for qemu-devel@nongnu.org; Tue, 09 Mar 2010 12:46:30 -0500 Received: from [199.232.76.173] (port=54848 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Np3Vl-0003hL-Tn for qemu-devel@nongnu.org; Tue, 09 Mar 2010 12:46:30 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Np3Vi-00005S-6D for qemu-devel@nongnu.org; Tue, 09 Mar 2010 12:46:29 -0500 Received: from mx20.gnu.org ([199.232.41.8]:9203) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Np3Vh-0008VW-O3 for qemu-devel@nongnu.org; Tue, 09 Mar 2010 12:46:25 -0500 Received: from sj-iport-1.cisco.com ([171.71.176.70]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Np3VV-0006w7-JZ for qemu-devel@nongnu.org; Tue, 09 Mar 2010 12:46:13 -0500 Message-ID: <4B968911.2050104@cisco.com> Date: Tue, 09 Mar 2010 10:44:49 -0700 From: "David S. Ahern" MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] EHCI support - device recognized, but no data References: <4B9077C9.4040309@cisco.com> <201003061925.01577@kevin-wolf.de> <4B938ECB.2060906@web.de> In-Reply-To: <4B938ECB.2060906@web.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka , Kevin Wolf Cc: qemu-devel@nongnu.org On 03/07/2010 04:32 AM, Jan Kiszka wrote: > Kevin Wolf wrote: >> Am Freitag, 5. März 2010 04:17 schrieb David S. Ahern: >>> Jan: >>> >>> I spent some more time on the EHCI support today. With the attached >>> patch (delta to the patch from yesterday) a USB key is recognized within >>> the guest (FC-12): >> >> Looks very nice. Actually I could access the file system on my USB stick. I >> have pushed your patch along with some additional minor changes to >> git://repo.or.cz/qemu/kevin.git ehci. Jan, you might want to pull from there. >> > > Merged, thanks. > > Meanwhile I played with some more devices, and I think I found one > scenario that should be handy to debug: -usbdevice net. Apparently, it > does not work yet, my console is just flooded with > >>>>>> ASYNC STATE MACHINE execute > 000.005 exec: ctr is 1 > 000.004 exec: frindex is 488,3 > 000.004 setting qh.current from 0E0B21E0 to 0x0E0B21E0 > 000.005 Active non-interrupt QH, executing > 000.003 pid is 1 > 000.00000.222 periodic state adv fr=490. [0E0B37A8] -> 00000001 > 000.009 periodic state adv fr=490. [0E0B37A8] -> 00000001 > 000.009 > >>>>>> ASYNC STATE MACHINE execute > 000.006 exec: ctr is 1 > 000.003 exec: frindex is 490,2 > 000.005 setting qh.current from 0E0B21E0 to 0x0E0B21E0 > 000.004 Active non-interrupt QH, executing > 000.004 pid is 1 > 000.004 calling dev->info->handle_packet > 000.004 exit loop dev->info->handle_packet > 000.003 Enter EXECUTING > 000.004 USBTRAN RSP NAK, returning without clear active > 000.004 finishing exec > 000.004 Nak occured and RL != 0, dec NakCnt to -1 > 000.004 write QH to VM memory > 000.203 periodic state adv fr=490. [0E0B37A8] -> 00000001 > 000.008 periodic state adv fr=490. [0E0B37A8] -> 00000001 > 000.009 > > Messages. The guest reports that it received one Ethernet packet, but > that's all, dhcpcd fails with a timeout. Already "ifconfig ethX up" > starts this flooding. > > Jan > What guest OS were you successful with for storage devices - windows or linux, 32-bit or 64? I've been mainly using FC-12, x86_64 as the guest OS, and an external (ie., physical) key of recent vintage. Qemu's msd device does not work with FC-12 (and UHCI). I played around with Qemu's usb-net device a bit, but not sure I am configuring it correctly (using monitor commands to attach). David