From owner-freebsd-hardware  Thu Apr  4 09:56:28 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA15006
          for hardware-outgoing; Thu, 4 Apr 1996 09:56:28 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA14993
          for <hardware@FreeBSD.org>; Thu, 4 Apr 1996 09:56:24 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id DAA24070; Fri, 5 Apr 1996 03:53:20 +1000
Date: Fri, 5 Apr 1996 03:53:20 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199604041753.DAA24070@godzilla.zeta.org.au>
To: Brett_Glass@ccgate.infoworld.com, bde@zeta.org.au,
        msmith@atrad.adelaide.edu.au
Subject: Re: Some solutions to disk problems.... I think.
Cc: hardware@FreeBSD.org, jkh@time.cdrom.com
Sender: owner-hardware@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> The per-drive wd flags are side effects of
>> hacks for ISA configuration.

>There are no exposed, per-drive wd flags.

They're there but not exposed by userconfig.  This must be why the
controller flags are abused to hold the drive flags.  The final
flags are:

drive 0: 32 bits of compile-time configurable drive flags
         | 16 low bits of configurable controller flags
drive 1: 32 bits of compile-time configurable drive flags
         | (16 high bits of configurable controller flags >> 16)

Bruce