From owner-freebsd-hackers  Fri Sep 20 19:29:33 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA14384
          for hackers-outgoing; Fri, 20 Sep 1996 19:29:33 -0700 (PDT)
Received: from Mail.IDT.NET (mail.idt.net [198.4.75.205])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA14339
          for <hackers@FreeBSD.org>; Fri, 20 Sep 1996 19:29:27 -0700 (PDT)
Received: from sequoia (ppp-12.ts-1.mlb.idt.net [169.132.71.12]) by Mail.IDT.NET (8.7.4/8.7.3) with SMTP id WAA13176; Fri, 20 Sep 1996 22:29:11 -0400 (EDT)
Message-ID: <32435339.15C2@mail.idt.net>
Date: Fri, 20 Sep 1996 22:30:17 -0400
From: Gary Corcoran <garycorc@mail.idt.net>
Reply-To: garycorc@mail.idt.net
X-Mailer: Mozilla 3.0 (WinNT; U)
MIME-Version: 1.0
To: Sujal Patel <smpatel@umiacs.umd.edu>
CC: janus@freegate.net, hackers@FreeBSD.org
Subject: Re: Plug and Play naivety
References: <Pine.OSF.3.91.960920162611.31553F-100000@mickey.umiacs.umd.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Sujal Patel wrote:
> 
> On Fri, 20 Sep 1996, Terry Lambert wrote:
> 
> > This exchange implies that the kernel will not use the PnP information
> > in the presence of a PnP BIOS to configure the drivers.  Can you confirm
> > or deny this?
> >
> > The benefit of the PnP code is not simply configuration of devices in
> > the absence of a PnP BIOS, but also in the provision of hints to the
> > device drivers.
> 
> The Plug & Play driver will eventually fill in isa_device structures for
> ISA devices properly.  If you chose not to configure your PnP device, it
> will read the configuration that is already there (i.e. the BIOS setup
> configuration).
> 
> You could further extend the model, by allowing the kernel to choose a
> device driver based on the information presented by the PnP aspect of the
> card (this is not planned for the first release).
> 

Is the (eventual) plan for the PnP code to allow kernel-config-specified
values to override those programmed by a PnP BIOS?  This would be
desirable to allow for fixing things when the BIOS botches its
automatic assignments (and/or I just want to specify, for example, my
own priorities for IRQs).

Gary