From owner-freebsd-hackers  Thu Jan  2 20:30:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id UAA27834
          for hackers-outgoing; Thu, 2 Jan 1997 20:30:13 -0800 (PST)
Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27829
          for <freebsd-hackers@freebsd.org>; Thu, 2 Jan 1997 20:30:11 -0800 (PST)
Received: (from henrich@localhost)
          by crh.cl.msu.edu (8.8.4/8.8.4)
	  id XAA20956; Thu, 2 Jan 1997 23:30:08 -0500 (EST)
From: Charles Henrich <henrich@crh.cl.msu.edu>
Message-Id: <199701030430.XAA20956@crh.cl.msu.edu>
Subject: Re: more than 32 disks?
To: dg@root.com
Date: Thu, 2 Jan 1997 23:30:08 -0500 (EST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199701030329.TAA18783@root.com> from David Greenman at "Jan 2, 97 07:29:46 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>   Oh yeah, I forgot to reply to your message to me about this. The answer for
> wcarchive is that we only have 3 controllers - 0-2, so I haven't been faced
> with an sd3<n> problem yet. :-) It looks like there are only 5 bits for the
> unit number. This means that one will have to make driver changes to go
> beyond 32 units. :-(

Hmm.  The system boot appears to assign the sd32 device just peachy, just
MAKEDEV dying.  I wonder what the adaptec driver is doing, guess its time to
scrounge around in code.

-Crh

       Charles Henrich     Michigan State University     henrich@msu.edu

                         http://pilot.msu.edu/~henrich