From owner-freebsd-mobile Sun Aug 25 5:44:17 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 502E937B400 for ; Sun, 25 Aug 2002 05:44:09 -0700 (PDT) Received: from insomnia.spc.org (insomnia.spc.org [195.224.94.183]) by mx1.FreeBSD.org (Postfix) with SMTP id 2212043E3B for ; Sun, 25 Aug 2002 05:44:07 -0700 (PDT) (envelope-from bms@insomnia.spc.org) Received: (qmail 22855 invoked by uid 1031); 25 Aug 2002 12:43:33 -0000 Date: Sun, 25 Aug 2002 13:43:33 +0100 From: Bruce M Simpson To: Bob Johnson Cc: Kevin Oberman , mobile@FreeBSD.ORG Subject: Re: Use of USB "Disk on a key" devices Message-ID: <20020825124332.GN27670@spc.org> References: <20020811235053.2E7935D04@ptavv.es.net> <20020813100445.GJ23205@spc.org> <3D68095B.3000106@garbonzo.hos.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D68095B.3000106@garbonzo.hos.ufl.edu> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bob, On Sat, Aug 24, 2002 at 06:31:55PM -0400, Bob Johnson wrote: > When you plug the device in to your system, it should be recognized. > with a log message something like > > Aug 20 22:56:06 bobj /kernel: da0: Removable Direct > Access SCSI-0 device Still no joy. I'd been meaning to do the standard DA_Q_NO_6_BYTE hack last time I left off with this. Although umass attaches to the device, the rest of the attach process doesn't go as expected (even when I do sysctl kern.cam.da.no_6_byte=1). For example:- umass1: M-Systems DiskOnKey, rev 1.10/2.00, addr 8 umass1: Get Max Lun not supported (SHORT_XFER) triage:~ % s camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 1 lun 0 (da1,pass1) triage:~ % s camcontrol inquiry 0:1:0 Exit 1 (Times out). Occasionally I'll see BBB resets being initiated by the umass driver. I've tried this with the DiskOnKey plugged into both a downstream hub and directly into the root hub itself. Running udesc_dump against the DiskOnKey when it's plumbed in as a ugen device gets interesting:- [..] Standard Interface Descriptor: [..] bInterfaceClass 08 bInterfaceSubClass 06 bInterfaceProtocol 50 [..] So it's being picked up by the umass driver based on its primary interface class and subclass, and 0x50 = 80 decimal, which is UPROTO_MASS_BBB_P, which means umass thinks it's an Iomega Zip 100. Since I got my MemoryStick and CompactFlash support sorted out, this isn't a priority for me, but if anyone else wants to have a shot, I will help where I can. BMS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message