From owner-freebsd-hardware  Sat Apr  6 11:36:39 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA12118
          for hardware-outgoing; Sat, 6 Apr 1996 11:36:39 -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 LAA12113
          for <hardware@freebsd.org>; Sat, 6 Apr 1996 11:36:36 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA07446; Sun, 7 Apr 1996 05:31:35 +1000
Date: Sun, 7 Apr 1996 05:31:35 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199604061931.FAA07446@godzilla.zeta.org.au>
To: Brett_Glass@ccgate.infoworld.com, msmith@atrad.adelaide.edu.au
Subject: Re: Some solutions to disk problems.... I think.
Cc: bde@zeta.org.au, hardware@freebsd.org, jkh@time.cdrom.com
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> The low and high words of the 'wdc' flags are implicitly exposed
>> per-drive 'wd' flags.

>I don't think so. It appears that there are 16 bits per controller
>(exposed) and then 8 bits per drive (stored in a different struct and
>unexposed). They're shifted and OR'ed together within the driver, but they
>seem to go into a local variable that's not preserved.

That's in the visual config.  The local variable is initialized to 0
and isn't passed on to the driver and isn't preserved.  The command
line config works.

Bruce