From owner-freebsd-current Sun Aug 26 15:14:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id A42EB37B405; Sun, 26 Aug 2001 15:14:13 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.135.64.Dial1.SanJose1.Level3.net [209.245.135.64]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id PAA09677; Sun, 26 Aug 2001 15:14:10 -0700 (PDT) Message-ID: <3B8974DC.57A9E085@mindspring.com> Date: Sun, 26 Aug 2001 15:14:52 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Kazutaka YOKOTA , Warner Losh , current@freebsd.org Subject: Re: unknown PNP hardware References: <200108262152.f7QLqar03411@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > > So, you are saying that this is because there is not a seperate > > "No BIOS" and "BIOS" section (or entry prefix) in the hints file, > > so that in a non-PnP system, both the "No BIOS" and "BIOS" > > entries will be examined, whereas on a PnP system, only the "BIOS" > > entries will be examined? > > This would be an unnecessary complication. I think the reason the hints are not just ignored is to allow people to fix "rogue" hardware. I'm willing to be corrected, since this looks like about 12 lines of code would make it ignore device.hints in the "PnP BIOS present" case. > > PS: The "BIOS" section could be shipped non-empty, if it had > > a "per-rogue" setion or prefix... then known broken PnP BIOS > > systems would "just work". > > The amount of work involved in making this "just work" would be pretty > enormous, and most of the applicable systems are approaching "relic" > status, making it hard to find them in order to debug. I wasn't suggesting that the work be done up front! This would have to be handled on a case-by-case basis, by the people having the problems with the defaults sending in their identifying information and the fix that works for them. It would only accumulate the knowledge of the rogues over an extended period of time, on an as-needed basis. Regards, -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message