From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I2qlL-0004w6-HK for qemu-devel@nongnu.org; Mon, 25 Jun 2007 11:45:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I2qlK-0004tG-3v for qemu-devel@nongnu.org; Mon, 25 Jun 2007 11:45:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I2qlJ-0004sb-RP for qemu-devel@nongnu.org; Mon, 25 Jun 2007 11:45:57 -0400 Received: from ebox1.ebox.com ([64.7.141.6] helo=ebox1b.ebox.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I2qlJ-0002Gt-Go for qemu-devel@nongnu.org; Mon, 25 Jun 2007 11:45:57 -0400 Received: from [192.168.1.3] (PC115.max-kade.uni-kiel.de [134.245.201.115]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ebox1b.ebox.com (Postfix) with ESMTP id A301217B43D for ; Mon, 25 Jun 2007 11:45:52 -0400 (EDT) Message-ID: <467FE32E.4040707@visible-assets.com> Date: Mon, 25 Jun 2007 17:45:50 +0200 From: Christopher Friedt MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] usb_host: only one interface supported 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 everyone, I'm trying to plug in a usb device (Motorola L2 phone, with micro usb connector). When I try to add it using the qemu console, usb_add host:22b8:4902 I get the response "usb_host: only one interface supported" in the standard output / error. What does this mean exactly? Is there some way I could patch my source code to allow this to work? I sort of got the impression that maybe the kernel had 'claimed' this device and therefore couldn't allow another app to address it directly. Is that the case? I also tried removing / adding the cdc_acm module and running it that way as a serial console, but for me (running motorola software update) it seems not to work Any suggestions? ~/Chris