From owner-freebsd-current Mon Jan 11 09:20:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01193 for freebsd-current-outgoing; Mon, 11 Jan 1999 09:20:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01183 for ; Mon, 11 Jan 1999 09:20:12 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (lh@bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id MAA04567 for ; Mon, 11 Jan 1999 12:00:40 -0500 (EST) Message-Id: <199901111700.MAA04567@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901110928.UAA17408@godzilla.zeta.org.au> Date: Mon, 11 Jan 1999 12:19:27 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: Re: ide_pci Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 It sounds like if DISABLE_PCI_IDE should be named something else, especially if it's going to be put in LINT. If its an option that fixes something in certain PCI IDE controllers, it sure sounds misleading. --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message