From owner-freebsd-hackers Mon Nov 13 1: 1:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 2CDFB37B4CF; Mon, 13 Nov 2000 01:01:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id IAA51179; Mon, 13 Nov 2000 08:58:00 GMT (envelope-from n_hibma@qubesoft.com) Date: Mon, 13 Nov 2000 08:58:00 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: James FitzGibbon Cc: Chris Dillon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: <20001112125403.A3835@targetnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In that case it might be that they are using some kind of private command to set the SCSI subsequently to different IDs. I'll check whether I have the device here and if so, I will try and snoop that command off the wire. Thanks for the pointer! Nick On Sun, 12 Nov 2000, James FitzGibbon wrote: > * Nick Hibma (n_hibma@qubesoft.com) [001112 06:01]: > > > I don't know. The only thing I know is that the protocol on the USB > > wire does not let you select the SCSI id, just the LUN. > > I've confirmed that under Windows this cable works with any SCSI ID, but > only if you install the Microtech driver. Otherwise, it doesn't show up > (i.e. identical to FBSD). Presuming that their driver is actually just a > ID mapping layer, would the same thing be feasible under BSD? > > I'll fire off a note to their support people and see if they can at least > confirm my line of thinking here. > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message