Messages in this thread |  | | Date | Fri, 6 Dec 1996 14:03:30 -0500 | From | Kenneth Albanowski <> |
| |
From kjahds Fri Dec 6 13:27:34 1996 X-Received: (from root@localhost) by kjahds.com (8.7.5/8.7.3) id NAA01921 for kjahds; Fri, 6 Dec 1996 13:27:33 -0500 X-Received: by tigger.jvnc.net id AA03555 (5.65c/IDA-1.4.4 for kjahds); Fri, 6 Dec 1996 13:30:23 -0500 X-Received: from nic.ott.hookup.net by tigger.jvnc.net with SMTP id AA03534 (5.65c/IDA-1.4.4 for kjahds@kjahds.com); Fri, 6 Dec 1996 13:30:18 -0500 X-Received: (aem@localhost) by nic.ott.hookup.net (8.8.4/1.212) id NAA17469 for kjahds@kjahds.com; Fri, 6 Dec 1996 13:30:07 -0500 (EST) Message-Id: <199612061830.NAA17469@nic.ott.hookup.net> Subject: Re: PNP patch into kernel when? To: kjahds@kjahds.com (Kenneth Albanowski) Date: Fri, 6 Dec 1996 13:30:04 -0500 (EST) From: "Andrew E. Mileski" <aem@nic.ott.hookup.net> Reply-To: aem@ott.hookup.net (Andrew E. Mileski) In-Reply-To: <Pine.LNX.3.93.961206100551.319A-100000@kjahds.com> from "Kenneth Albanowski" at Dec 6, 96 10:07:10 am X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit ReSent-Date: Fri, 6 Dec 1996 14:03:26 -0500 (EST) ReSent-From: Kenneth Albanowski <kjahds@kjahds.com> ReSent-To: linux-kernel@vger.rutgers.edu ReSent-Subject: ReSent-Message-ID: <Pine.LNX.3.93.961206140326.319L@kjahds.com>
> Hmm. I suppose I should ask this, and you can elucidate the kernel list > with your answer: what about a piece of hardware like a NodeRunner > (EEPROM configurable NE2000 clone). It's not PnP, but it is soft > configurable. How does that fall into your resource management scheme?
Sure...but I'd prefer to do it in the future on the pnp-list :-) I don't want to monopolize linux-kernel.
The PCI example: The configuration manager (CM) says, "Hey, there is an NE2000 card here. We need a NE2000 driver, so I'll tell kerneld (and/or the user)."
Your example: The driver says, "Hey, is there any kind of NE2000 device on the system?". The CM responds "yes", or "no". If "no", the driver says to the CM, "okay, then I'm gonna search for one myself - just in case". If the driver finds a device, it tells the CM, "btw, there is an NE2000 card attached, and it is using the following hardware resources..." The CM thanks the driver kindly, and the rest of the PnP configuration sequence is then followed.
Howzat?
Note: There will likely be 2 differnet configuration managers in the system. The first one will handle simple configuration at boot, and will be part of the kernel. The second one will handle post-boot configuration (example: docking stations), and will be a user-space program. It will handle the complex configuration of devices. To a driver though, they will look as one CM.
-- Andrew E. Mileski mailto:aem@ott.hookup.net Linux Plug-and-Play Kernel Project http://www.redhat.com/linux-info/pnp/ XFree86 Matrox Team http://www.bf.rmit.edu.au/~ajv/xf86-matrox.html
|  |