From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EYQvj-0005mn-Kh for qemu-devel@nongnu.org; Sat, 05 Nov 2005 11:30:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EYQvi-0005mS-4b for qemu-devel@nongnu.org; Sat, 05 Nov 2005 11:30:11 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EYQvh-0005mP-W5 for qemu-devel@nongnu.org; Sat, 05 Nov 2005 11:30:10 -0500 Received: from [212.227.126.186] (helo=moutng.kundenserver.de) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EYQvh-0006kW-U9 for qemu-devel@nongnu.org; Sat, 05 Nov 2005 11:30:10 -0500 From: Volker Ruppert Subject: Re: [Qemu-devel] USB support Date: Sat, 5 Nov 2005 17:31:24 +0100 References: <436CC599.3080905@bellard.org> In-Reply-To: <436CC599.3080905@bellard.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511051731.24176.info@vruppert.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, > The following features are implemented: > > - PCI UHCI USB controller (I finally decided to implement UHCI because I > know it better than OHCI and because Bochs has a similar driver. Of > course it would still be very interesting to have an equivalent OHCI > controller for non PC targets and an EHCI controller for USB 2.0 devices). I compared the Qemu USB controller with the Bochs one using Ralph Brown's pcifg utility and found two different things. - Bochs USB appears at function 2 of the PIIX3 - Bochs USB uses PIRQ line INTD You can find both things in the PIIX3 documentation. I tried the Qemu USB implementation with Win98 here. The hubs are detected correctly, but it makes Win98 hang on shutdown. > - Linux host USB redirector to use the USB 1.1 host devices which are > not requested by the host OS (i.e. no host driver is loaded for them). > It is *very* limited and buggy at the moment, but I was able (once !) to > mount a disk-on-key flash device. I guess the host OS doesn't like modifing data on a mounted devices. It might be okay for input-only devices. I cannot try it here, since it requires root permissions. -- Bye Volker