Date: Wed, 6 Aug 1997 12:42:02 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: ggm@connect.com.au (George Michaelson) Cc: current@FreeBSD.ORG Subject: Re: canonical issue wrt DMA & wd/wdc Message-ID: <199708060312.MAA02887@genesis.atrad.adelaide.edu.au> In-Reply-To: <199708060146.LAA18653@broon.off.connect.com.au> from George Michaelson at "Aug 6, 97 11:46:47 am"
next in thread | previous in thread | raw e-mail | index | archive | help
George Michaelson stands accused of saying: > > 1) can somebody add the DMA warning issues to an FAQ so we can understand > when it really means "DMA is disabled" as opposed to "your m.b. or BIOS > doesn't support enabling, who knows, lets wing it" 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. > 2) flags 0x80ff80ff blows up in config on wdc but works on wd<n> instances This is nonsense; you can't put flags on 'wd' instances, and it works fine on 'wdc' (the only place you _can_ put it). > 3) assuming when an ASUS m.b. reports the disks are mode4 compliant its not > lying, does adding the flags buy me anything Which flags? The 80ff flags for each channel are required for 32-bit and multi-block mode to be used, yes. > 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) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708060312.MAA02887>