From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M3rUK-0006aJ-GE for qemu-devel@nongnu.org; Tue, 12 May 2009 08:53:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M3rUG-0006X4-U8 for qemu-devel@nongnu.org; Tue, 12 May 2009 08:53:40 -0400 Received: from [199.232.76.173] (port=49959 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M3rUG-0006Ws-On for qemu-devel@nongnu.org; Tue, 12 May 2009 08:53:36 -0400 Received: from smtp-out1.tiscali.nl ([195.241.79.176]:33916) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M3rUF-00018Y-Ge for qemu-devel@nongnu.org; Tue, 12 May 2009 08:53:35 -0400 Subject: Re: [Qemu-devel] [PATCH] EHCI emulation module for review From: Paul Bolle In-Reply-To: <1295ed070905120536n50ace3fdx9903034ab339159a@mail.gmail.com> References: <1240874133.28148.62.camel@x41.thuisdomein> <1242120767.7568.18.camel@localhost.localdomain> <1295ed070905120536n50ace3fdx9903034ab339159a@mail.gmail.com> Content-Type: text/plain Date: Tue, 12 May 2009 14:53:32 +0200 Message-Id: <1242132812.2106.8.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pantelis Koukousoulas Cc: Mark Burkley , qemu-devel@nongnu.org On Tue, 2009-05-12 at 15:36 +0300, Pantelis Koukousoulas wrote: > Well, at least for me the EHCI patch didn't work at all (neither in > winxp guests nor in Linux) last time I tried. The fact you got it to > work is encouraging. 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 ...). Paul Bolle