Date: Wed, 06 Aug 1997 13:15:39 +1000 From: George Michaelson <ggm@connect.com.au> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: current@freebsd.org Subject: Re: canonical issue wrt DMA & wd/wdc Message-ID: <19569.870837339@connect.com.au> In-Reply-To: Your message of "Wed, 06 Aug 1997 12:42:02 %2B0930." <199708060312.MAA02887@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19569.870837339>