From owner-freebsd-questions  Thu Jul 24 07:19:34 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA00650
          for questions-outgoing; Thu, 24 Jul 1997 07:19:34 -0700 (PDT)
Received: from oneway.com (oneway.com [198.80.68.27])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA00643;
          Thu, 24 Jul 1997 07:19:30 -0700 (PDT)
Received: from oneway.com (oneway.com [198.80.68.27]) by oneway.com (8.8.5/8.8.3) with SMTP id JAA14701; Thu, 24 Jul 1997 09:13:27 -0500 (CDT)
Date: Thu, 24 Jul 1997 09:13:27 -0500 (CDT)
From: Jay Kuri <jaykuri@oneway.com>
To: Peter Dufault <dufault@hda.com>
cc: freebsd-scsi@FreeBSD.ORG, questions@FreeBSD.ORG
Subject: Re: help: wiring down scsi devices doesn't work
In-Reply-To: <199707221118.HAA06466@hda.hda.com>
Message-ID: <Pine.BSF.3.95q.970724091056.14644B-100000@oneway.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> >     I have been trying, to no avail, to wire down a particular target
> > device to pt0.  Although config gives me no errors, and the kernel
> > rebuilds fine, it does not wire down the device... and instead reports it
> > (a scsi scanner) as uk0.  
> It didn't recognize it as a processor type. The device still needs
> to claim to be a processor type for the kernel to connect it as
> that.

    Gotcha...  I was under the impression that the scanner was reporting
itself as a processor (and this is what the docs for the driver said it
would do)  but it was really reporting itself as a type 6 (scanner...
imagine that :)  
    I thought that processor target and unknown target had some different
functionality... It appears that I am wrong in that.

Thanks for your help,

Jay