From owner-freebsd-current  Mon Jan 11 01:29:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA06164
          for freebsd-current-outgoing; Mon, 11 Jan 1999 01:29:16 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06156
          for <freebsd-current@FreeBSD.ORG>; Mon, 11 Jan 1999 01:29:14 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA17408;
	Mon, 11 Jan 1999 20:28:31 +1100
Date: Mon, 11 Jan 1999 20:28:31 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901110928.UAA17408@godzilla.zeta.org.au>
To: ijliao@dragon2.net, lcremean@tidalwave.net
Subject: Re: ide_pci
Cc: culverk@wam.umd.edu, freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> > options DISABLE_PCI_IDE
>> 
>> i have a question :
>> since this options can solve 2nd ide channel problem, why not introduce this
>> options in LINT ?
>
>This does sound like a good idea to me, but I think there's already been a
>fix committed to wd.c for it. Apparently 
>
>options ALI_V
>
>also does the trick, if you have version 1.182 of wd.c (do ident
>/sys/i386/isa/wd.c to check).

Both of these options are bogus.  DISABLE_PCI_IDE works by arranging
for buggy code in wdprobe() to not be run.  It doesn't actually disable
PCI IDE, since simiilar but non-buggy code in wdgetctlr() is still run.
It disables buggy support for (Promise only?) IDE interfaces with more
than 4 devices.  PCI IDE is disabled by not enabling it in the wdc flags.
ALI_V has no effect except to obfuscate the code.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message