From owner-freebsd-current  Tue Aug  5 20:17:04 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA24157
          for current-outgoing; Tue, 5 Aug 1997 20:17:04 -0700 (PDT)
Received: from broon.off.connect.com.au (broon.off.connect.com.au [203.63.69.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24150
          for <current@freebsd.org>; Tue, 5 Aug 1997 20:16:59 -0700 (PDT)
Received: from connect.com.au (ggm@localhost) by broon.off.connect.com.au with ESMTP id NAA19577
  (8.8.5/IDA-1.6); Wed, 6 Aug 1997 13:15:44 +1000 (EST)
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: current@freebsd.org
Subject: Re: canonical issue wrt DMA & wd/wdc 
In-reply-to: Your message of "Wed, 06 Aug 1997 12:42:02 +0930."
             <199708060312.MAA02887@genesis.atrad.adelaide.edu.au> 
Date: Wed, 06 Aug 1997 13:15:39 +1000
Message-ID: <19569.870837339@connect.com.au>
From: George Michaelson <ggm@connect.com.au>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  If you are running -current you are expected to be able to work this
  sort of thing out for yourself.  Adding diagnostic messages from a
  developmental driver to the FAQ is stupid.

Point taken.
  
  This is nonsense; you can't put flags on 'wd' instances, and it works
  fine on 'wdc' (the only place you _can_ put it).

Goest thou and read LINT. I'm afraid you can flag wd0 as well as wdc0 
and as I said, flag wdc0 broke for me. Its highly position specific and
by adding said word, config blew up at me.
  
  Which flags?  The 80ff flags for each channel are required for 32-bit
  and multi-block mode to be used, yes.

Yes, but in the absence of any guidance, what does it buy me? I'm down-speeding
from SPARCland where its all moot. I am not clue-dense with respect to the
advantages one way or another. 
  
  > 4) claims LINT explains how to enable new/untrustworthy DMA are untrue as
  >    far as I can see (but then I'm hyper dumb :-)
  
  Read the commit message, or wait for the final version of the code 8)

Impatience tending to a maximum.

Bit concerned you abjure flags can't on devices and can on controllers. Tain't
what I see since cvsup last night.

-George