From owner-freebsd-current@FreeBSD.ORG Mon Jan 3 21:59:28 2005 Return-Path: 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 816C716A4CE; Mon, 3 Jan 2005 21:59:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0626343D1D; Mon, 3 Jan 2005 21:59:28 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j03M24Om010532; Mon, 3 Jan 2005 15:02:04 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41D9BFDC.1050304@freebsd.org> Date: Mon, 03 Jan 2005 14:57:48 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ticso@cicely.de References: <20050103205820.GA74545@users.altadena.net> <20050103214607.GB64429@cicely12.cicely.de> In-Reply-To: <20050103214607.GB64429@cicely12.cicely.de> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hardware@freebsd.org cc: Pete Carah cc: current@freebsd.org Subject: Re: Adaptec USB2Xchange X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 21:59:28 -0000 Bernd Walter wrote: > On Mon, Jan 03, 2005 at 12:58:20PM -0800, Pete Carah wrote: > >>I have reason to use a USB to SCSI adapter under FBSD. I have a USB2Xchange >>from Adaptec, but (as usual for adaptec) it requires a firmware load, which >>appears harder in usb than in PCI. Does anyone know how to do this? (Should >>we have a generic firmware loader similar in concept to the ndis converter?) >> >>A not-as-preferred alternative would be a PC card scsi unit; this won't >>work on the desktop computers, though. >> >>For my immediate application (streaming tape) I could tolerate a userland >>driver under ugen. For disks this wouldn't work without a more general >>kernel block-device structure (or a userland link back to the cam/xpt layer, >>analogous to the tunnel net driver, which couldn't be *too* hard and could >>be desirable). >> >>Kernel attach message is: >>ugen0: Adaptec product 0x2002, rev 2.00/1.00, addr 2 >> >>My kernel has ugen/umass/uhid/ums/ucom/uplcom/umodem compiled in, so >>this (which should show somewhere?) isn't being recognized. > > > As far as I know the Adaptec parts can do multiple addreses, which is > not part of umass specification. > They may use a vendor extended umass or completely different protocol. > Whatever it is - the device doesn't offer itself as beeing umass. > With vendor specs it should be simple to teach our umass driver about > this special device, even if it really isn't umass. > Also firmware uploading in USB is very simple if you have vendor specs. > Without specs all you can do is sniff Windows data and guess. > Getting specs out of Adaptec is about as fun as digging through granite with a spoon. Most of the "Adaptec" products that are found on store shelves these days are just rebranded from other vendors, so it might be more fruitful to discover the OEM of this part and bother that vendor for specs. There doesn't appear to be a driver in the linux tree for this either, at least not for the Adaptec name of it. Scott