From owner-freebsd-hardware  Thu Apr  4 14:14:55 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA07914
          for hardware-outgoing; Thu, 4 Apr 1996 14:14:55 -0800 (PST)
Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA07904
          for <hardware@FreeBSD.org>; Thu, 4 Apr 1996 14:14:52 -0800 (PST)
Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp
	(Smail3.1.29.1 #12) id m0u4xJI-000wrGC; Thu, 4 Apr 96 14:15 PST
Received: from cc:Mail by ccgate.infoworld.com
	id AA828655952; Thu, 04 Apr 96 14:52:50 PST
Date: Thu, 04 Apr 96 14:52:50 PST
From: "Brett Glass" <Brett_Glass@ccgate.infoworld.com>
Message-Id: <9603048286.AA828655952@ccgate.infoworld.com>
To: Bruce Evans <bde@zeta.org.au>, bde@zeta.org.au,
        msmith@atrad.adelaide.edu.au
Cc: hardware@FreeBSD.org, jkh@time.cdrom.com
Subject: Re: Some solutions to disk problems.... I think.
Sender: owner-hardware@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> 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)

Exactly. I found these while browsing through the code. My changes to wd.c
use two controller flags to indicate the desire to turn off inactivity
timeouts, and one flag in each drive's hidden drive word to indicate
success (so that status can be checked and/or reported later). It'd be nice
to use just the drive flags, but there has to be a way for the user to set
or clear the option on a per-drive basis.

--Brett