* [Qemu-devel] Isochronous problem with usb OHCI
@ 2008-11-17 13:35 ML_PierreLeMagourou
0 siblings, 0 replies; 3+ messages in thread
From: ML_PierreLeMagourou @ 2008-11-17 13:35 UTC (permalink / raw)
To: qemu-devel@nongnu.org
Hi,
I try to use a webcam (logitech E 3500) through Qemu USB OHCI and have a problem with isochronous frames. Here is a little description :
When Isochronous traces are activated I can see that isochronous packets come from the host (async_complete function in usb-linux.c). These packets are then completed in hw/usb-ohci.c, there it calls ohci_process_lists function with completion parameter set to 1. The problem is that it then does not call the ohci_service_ed_list function in order to finish the isochronous packet completion and send it to the target. The OHCIState->ctl is neither a control nor a bulk list.
In fact, I wonder what is the normal behavior for an isochronous packet completion. Does someone have had a similar problem with isochronous frames when using usb ohci ?
--
Pierre
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Qemu-devel] Isochronous problem with usb OHCI
@ 2008-11-17 16:20 Pierre Le Magourou
2008-12-09 13:33 ` baibai_tao
0 siblings, 1 reply; 3+ messages in thread
From: Pierre Le Magourou @ 2008-11-17 16:20 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Hi,
I try to use a webcam (logitech E 3500) through Qemu USB OHCI and have a
problem with isochronous frames. Here is a little description :
When Isochronous traces are activated I can see that isochronous packets
come from the host (async_complete function in usb-linux.c). These packets
are then completed in hw/usb-ohci.c, there it calls ohci_process_lists
function with completion parameter set to 1. The problem is that it then
does not call the ohci_service_ed_list function in order to finish the
isochronous packet completion and send it to the target. The OHCIState->ctl
is neither a control nor a bulk list.
In fact, I wonder what is the normal behavior for an isochronous packet
completion. Does someone have had a similar problem with isochronous frames
when using usb ohci ?
--
Pierre
[-- Attachment #2: Type: text/html, Size: 876 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Isochronous problem with usb OHCI
2008-11-17 16:20 [Qemu-devel] Isochronous problem with usb OHCI Pierre Le Magourou
@ 2008-12-09 13:33 ` baibai_tao
0 siblings, 0 replies; 3+ messages in thread
From: baibai_tao @ 2008-12-09 13:33 UTC (permalink / raw)
To: qemu-devel
I met the same problem when using usb-ohci.c with usb-linux.c and usb.c in
head version.
Comparing usb-ohci.c on head and in 0.9.1, there is little difference but
the other 2 files are totally different.
It could work if I pickup usb-linux.c and usb.c from 0.9.1.
Pierre Le Magourou wrote:
>
> Hi,
>
> In fact, I wonder what is the normal behavior for an isochronous packet
> completion. Does someone have had a similar problem with isochronous
> frames
> when using usb ohci ?
>
> --
> Pierre
>
>
--
View this message in context: http://www.nabble.com/Isochronous-problem-with-usb-OHCI-tp20542659p20914766.html
Sent from the QEMU - Dev mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-12-09 13:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-17 16:20 [Qemu-devel] Isochronous problem with usb OHCI Pierre Le Magourou
2008-12-09 13:33 ` baibai_tao
-- strict thread matches above, loose matches on Subject: below --
2008-11-17 13:35 ML_PierreLeMagourou
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).