From: Pantelis Koukousoulas <pktoss@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Mark Burkley <qemu@emutex.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] EHCI emulation module for review
Date: Tue, 12 May 2009 16:01:45 +0300 [thread overview]
Message-ID: <1295ed070905120601s4c3c94e8g5e198b6b7a993636@mail.gmail.com> (raw)
In-Reply-To: <1242132812.2106.8.camel@localhost.localdomain>
> See my message of (about) two weeks ago about all the things I needed to
> do to get to a patch that actually applied, compiled without (qemu's
> default) warnings and didn't segfault immediately.
>
> If you still have trouble to get it to work against the current master
> branch (or do not feel like manually correcting the patch) I could post
> what worked for me (where worked means: at least doesn't segfault
> immediately, but will run into issues sooner or later ...).
The problem could be that we have different definitions of "working".
What happened in my case was that the patch applied and compiled
(after some trivial messing around) and there were no segfaults.
The controller saw the devices in the windows guest, but could
not complete the driver registration process, so it eventually gave
up and windows returned the "I could not make this hardware work"
message. It looks like the reason for this failure was that some
URBs did not really make it to the device (or back) but I didn't
have the time to investigate more thoroughly yet.
Did you get it to run all the way to devices working normally?
Cheers,
Pantelis
next prev parent reply other threads:[~2009-05-12 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 0:05 [Qemu-devel] [PATCH] EHCI emulation module for review Mark Burkley
2008-11-01 11:13 ` Daniel Godás
2008-11-01 22:19 ` Mark Burkley
2009-04-27 23:15 ` Paul Bolle
2009-05-12 9:32 ` Paul Bolle
2009-05-12 12:36 ` Pantelis Koukousoulas
2009-05-12 12:53 ` Paul Bolle
2009-05-12 13:01 ` Pantelis Koukousoulas [this message]
2009-05-12 15:46 ` Paul Bolle
2009-11-11 22:41 ` Michael Trimarchi
2009-11-12 15:23 ` Michael Trimarchi
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=1295ed070905120601s4c3c94e8g5e198b6b7a993636@mail.gmail.com \
--to=pktoss@gmail.com \
--cc=pebolle@tiscali.nl \
--cc=qemu-devel@nongnu.org \
--cc=qemu@emutex.com \
/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).