From owner-freebsd-current Sun Sep 26 12: 6:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 1800A14ED0 for ; Sun, 26 Sep 1999 12:06:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA13355; Sun, 26 Sep 1999 11:59:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909261859.LAA13355@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dmaddox@conterra.com Cc: current@FreeBSD.ORG Subject: Re: Loss of Functionality with newpnp In-reply-to: Your message of "Sun, 26 Sep 1999 14:55:57 EDT." <19990926145557.B430@dmaddox.conterra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Sep 1999 11:59:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote: > > > > PnP is an infrastructure facility used by drivers to detect and > > configure hardware. The side-effect you were relying on was that the > > old code would indiscriminately configure any and all PnP hardware > > regardless of whether a driver had requested it to. > > Why is this not desirable? I've already asked you to do your own research, and I meant it. The simple answer is "if we don't have a [working] driver for it, we don't want it". -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message