Date: Sat, 26 Jun 1999 10:34:11 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: takawata@shidahara1.planet.sci.kobe-u.ac.jp Cc: hackers@freebsd.org Subject: Re: NEWBUS-ifyed ISA-PnP Question. Message-ID: <Pine.BSF.4.05.9906261031150.80685-100000@herring.nlsystems.com> In-Reply-To: <199906251733.CAA12146@libr.scitec.kobe-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 26 Jun 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: > Hi, > > I believe someone working on NEWBUS-ifying ISA-PnP. > How will they implement it? > I think current framework is like this. > +--------+ +--------+ > ...|ISA DEV | |ISA-hint|<-This device provides > +--------+ +--------+ what device is connected > | | | the ISA bus. > ----------ISA-------------- > | > +-------------+ > |Nexus or ISAB| > +-------------+ > > > 1. Is the figure true? > 2.If so,where do they attach ISA-PnP mechanism? > attach it like ISA-hint device,modify ISA Bus code or isapnpbus > other than ISA-Bus? > 3.How do I add ISA-PnP device? > 4.How do I add PnP mechanism other than ISA-PnP. This diagram is correct. The ISA-PnP driver is similar to the ISA-hint driver in that it doesn't probe and attach devices itself but creates devices which other drivers can attach to. I have modified the api between the ISA device enumerators (ISA-hint and ISA-PnP) to allow them to specify a set of resource alternatives and a callback function which can select a single alternative. Other PnP mechanisms should fit into this scheme easily. I had ACPI in mind when I was putting this system together. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906261031150.80685-100000>