qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] EHCI support - device recognized, but no data


From: David S. Ahern
Subject: Re: [Qemu-devel] [PATCH] EHCI support - device recognized, but no data
Date: Tue, 09 Mar 2010 10:44:49 -0700
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3




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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]