From owner-freebsd-hardware@FreeBSD.ORG  Mon Jan  3 20:58:20 2005
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7574716A4CE; Mon,  3 Jan 2005 20:58:20 +0000 (GMT)
Received: from users.altadena.net (users.altadena.net [207.151.161.11])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4ACEF43D3F; Mon,  3 Jan 2005 20:58:20 +0000 (GMT)
	(envelope-from pete@users.altadena.net)
Received: from pete by users.altadena.net with local (Exim 4.43)
	id 1ClZHQ-000Jpq-3x; Mon, 03 Jan 2005 12:58:20 -0800
Date: Mon, 3 Jan 2005 12:58:20 -0800
From: Pete Carah <pete@altadena.net>
To: hardware@freebsd.org, current@freebsd.org
Message-ID: <20050103205820.GA74545@users.altadena.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: Pete Carah <pete@users.altadena.net>
Subject: Adaptec USB2Xchange
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2005 20:58:20 -0000

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.

1. Has anyone else tried this (or wanted to...)?
2. Absent a way to use this device, what would work (I know about slimscsi;
   it is less desirable since I can't use it on my desktop systems)?

-- Pete