From owner-freebsd-current Sun Dec 1 20:54:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7478637B401; Sun, 1 Dec 2002 20:54:37 -0800 (PST) Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF7D243EB2; Sun, 1 Dec 2002 20:54:36 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: from ns.altadena.net (localhost [127.0.0.1]) by ns.altadena.net (8.12.6/8.12.3) with ESMTP id gB24sQpv079177; Sun, 1 Dec 2002 20:54:26 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.12.6/8.12.3/Submit) id gB24sPIO079176; Sun, 1 Dec 2002 20:54:25 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200212020454.gB24sPIO079176@ns.altadena.net> Subject: USB mass device not quite there To: stable@freebsd.org, current@freebsd.org Date: Sun, 1 Dec 2002 20:54:25 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Pardon sending this to both stable and current, but this is relevant to both and the code paths may be different... I just acquired a usb "mass" device which partly identifies. This is a "Dazzle" multi-card reader. The CF slot works fine; identifies as da0, and though it is slower than the cf pcmcia adapter, does work. (my crazy Vaio R505 still doesn't handle any pcmcia/cardbus in either stable or current; the first usb works fine in both stable and current, and both the internal memorystick device and firewire work in current but not stable.) console output (with a 128mb cf card present on insertion) is: -------------------------------------------------------------- umass0: SCM Microsystems Inc. eUSB ORCA Quad Reader, rev 1.10/5.07, addr 2 umass0:1:0:-1: Attached to scbus1 as device 0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-2 device pass0: Serial Number 21M82CFC1Y09C11125Z3 pass0: 650KB/s transfers Creating DISK da0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: Serial Number 21M82CFC1Y09C11125Z3 da0: 650KB/s transfers da0: 122MB (250368 512 byte sectors: 64H 32S/T 122C) umass0: Invalid CSW: tag 0 should be 11 da0s1: type 0x6, start 32, end = 250111, size 250080 : OK umass0: Invalid CSW: tag 0 should be 11728 ------------------------------------------ The Invalid CSW messages seem to not affect anything, but they probably shouldn't be there either... I do see the code that prints it but don't know enough about the umass spec to tell anything. The other slot is multiple; it handles SmartMedia, MM/SD cards, and memory-sticks. It is not found by the usb event handler or camcontrol at all. The directions do say that this device shows up in windoze as 2 drives (I haven't tried it yet, under any of 95, 98, or XP). Apparently our usb event handler doesn't expect to find 2 devices, or pass doesn't expect 2 devices beyond it in a single scan? One thing I don't know about this device is whether it looks like 2 usb devices, or a single pass device with 2 da devices, or a drive with 2 lun's (I can't think of any other possiblilties, though there may be more). I also don't know how to tell from the output of usbd with lots of -v's and/or camcontrol with lots of -v's; both only find one thing from this adapter as far as I can see. What do I compile with more debug flags turned on? usb.c and umass.c, I presume; usbd appears to just want more -v's for that effect. Or, is there a quirk entry that could be done to make this thing show up right? Or do multiple devices just not work, like modem/enet combo cards under OLDCARD? -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message