From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KbhvO-0002ep-9d
	for qemu-devel@nongnu.org; Fri, 05 Sep 2008 16:28:58 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KbhvN-0002eO-22
	for qemu-devel@nongnu.org; Fri, 05 Sep 2008 16:28:57 -0400
Received: from [199.232.76.173] (port=57806 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KbhvM-0002eL-Qd
	for qemu-devel@nongnu.org; Fri, 05 Sep 2008 16:28:56 -0400
Received: from [67.18.187.6] (port=50618 helo=tjworld.net)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <linux@tjworld.net>) id 1KbhvM-0004Wc-Py
	for qemu-devel@nongnu.org; Fri, 05 Sep 2008 16:28:56 -0400
Subject: Re: [Qemu-devel] [PATCH] Add USB sys file-system support (v2)
From: TJ <linux@tjworld.net>
In-Reply-To: <48C1862C.3050307@windriver.com>
References: <1220571341.2638.6.camel@hephaestion>
	<1220580385.2638.15.camel@hephaestion> <48C1346F.3000405@windriver.com>
	<1220640699.5470.15.camel@hephaestion> <48C1862C.3050307@windriver.com>
Content-Type: text/plain
Date: Fri, 05 Sep 2008 21:28:51 +0100
Message-Id: <1220646531.9611.8.camel@hephaestion>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>

On Fri, 2008-09-05 at 14:19 -0500, Jason Wessel wrote:
> > What version of kvm, or what was the commit HEAD hash?
> >   
> 
> Since you posed this to the qemu-devel mailing list, I tried it on the
> QEMU development head.

I've posted to qemu-devel and kvm-devel, working primary with the kvm
release packaging it for Ubuntu Gutsy/Hardy/Intrepid.

> 
> > What does the patch report as the method of access to the USB
> > file-system? 
> husb: using /dev/bus/usb
> 
> > Does the same device work without the patch? 
> 
> Of course not, because the host does not have /proc/bus/usb.

If you're using Ubuntu you can easily test with /proc/bus/usb by editing
the comments out to enable the 'magic lines' in 
/etc/init.d/mountdevsubfs.sh or issue them manually:

#
# Magic to make /proc/bus/usb work
#
#mkdir -p /dev/bus/usb/.usbfs
#domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
#ln -s .usbfs/devices /dev/bus/usb/devices
#mount --rbind /dev/bus/usb /proc/bus/usb


> What might be a defect is that it did not work with the
> |host:vendor_id:product_id and immediately failed.

Yes, I've been looking at that. Although the code-path goes through the
patch - usb_host_scan() - it simply passed the structures and function
pointer on without touching them. I'm currently analysing it with some
dprintf() entries to see why usb_host_find_device() doesn't get the
device.

> I am guessing it is unique to this class of device or perhaps even this
> particular device.

I agree, maybe it is the serial character-based devices. As I can
reproduce it with a different VID:PID of the same class it seems more
likely.