From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 3 00:28:38 2005 Return-Path: X-Original-To: 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 99FE716A420; Sun, 3 Jul 2005 00:28:38 +0000 (GMT) (envelope-from ps@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E2CC4400F; Sun, 3 Jul 2005 00:17:42 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id 80B4C61334; Sat, 2 Jul 2005 17:16:58 -0700 (PDT) X-Original-To: ps@mu.org Delivered-To: ps@mu.org Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by elvis.mu.org (Postfix) with ESMTP id CDBDE5C9C1 for ; Mon, 3 Jan 2005 13:47:50 -0800 (PST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 8A5D0569E5; Mon, 3 Jan 2005 21:47:38 +0000 (GMT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D81DC16A4D5; Mon, 3 Jan 2005 21:47:34 +0000 (GMT) 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 8E8DF16A4CE; Mon, 3 Jan 2005 21:47:03 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAE3243D1D; Mon, 3 Jan 2005 21:47:02 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) j03LkVHo043455 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 3 Jan 2005 22:46:32 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id j03LkBXX007687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jan 2005 22:46:11 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id j03LkABF070396; Mon, 3 Jan 2005 22:46:10 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id j03Lk9gP070395; Mon, 3 Jan 2005 22:46:09 +0100 (CET) (envelope-from ticso) From: Bernd Walter To: Pete Carah Message-ID: <20050103214607.GB64429@cicely12.cicely.de> References: <20050103205820.GA74545@users.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050103205820.GA74545@users.altadena.net> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on elvis.mu.org X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Level: Cc: hardware@freebsd.org, current@freebsd.org Subject: Re: Adaptec USB2Xchange X-BeenThere: freebsd-hardware@freebsd.org Reply-To: ticso@cicely.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Sun, 03 Jul 2005 00:28:39 -0000 X-Original-Date: Mon, 3 Jan 2005 22:46:08 +0100 X-List-Received-Date: Sun, 03 Jul 2005 00:28:39 -0000 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. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"