From: baibai_tao <baibai_tao@163.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Isochronous problem with usb OHCI
Date: Tue, 9 Dec 2008 05:33:10 -0800 (PST) [thread overview]
Message-ID: <20914766.post@talk.nabble.com> (raw)
In-Reply-To: <84501dc10811170820q5003cb44j91df9026fb419c9b@mail.gmail.com>
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.
next prev parent reply other threads:[~2008-12-09 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 16:20 [Qemu-devel] Isochronous problem with usb OHCI Pierre Le Magourou
2008-12-09 13:33 ` baibai_tao [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-17 13:35 ML_PierreLeMagourou
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=20914766.post@talk.nabble.com \
--to=baibai_tao@163.com \
--cc=qemu-devel@nongnu.org \
/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).