Date: Wed, 10 Jul 1996 23:05:13 -0700 From: Amancio Hasty <hasty@rah.star-gate.com> To: Sujal Patel <smpatel@umiacs.umd.edu> Cc: hackers@freebsd.org Subject: Re: Puting PnP support into -current by default Message-ID: <199607110605.XAA12428@rah.star-gate.com> In-Reply-To: Your message of "Wed, 10 Jul 1996 22:18:09 PDT." <Pine.NEB.3.92.960710221525.176A-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Mea Culpa... I doubt that there are many devices more complex to configure than the GUS PnP. What I am demonstrating by example and can be easily extended to a more general case, is for a tighter integration between the drivers and the PnP code. It seems to me that the decision to decide what to configure in PnP devices should be localized to the driver. Regards, Amancio >From The Desk Of Sujal Patel : > On Wed, 10 Jul 1996, Amancio Hasty wrote: > > > > > device gus0 at isa? port 0x220 irq 11 drq 5 flags 0x7 vector gusintr > > > > In this case, the gus driver at probe times calls the PnP routines however > > it uses the configuration values pass to the driver to activate and > > configure the GUS PnP. > > Unfortunately, simplify it down to a simple case like this isn't easy AT > ALL. There are things like logical devices, multiple irqs/drqs, serial > numbers, and zillions of other things that need to be handled. Also, the > code needs to be generic enough to handle all ISA PnP devices. > > I'll try to speed up development on this stuff a bit, but I'm still a bit > off from being ready to commit. Unless someone *really* wants to see the > stuff "kludged" into -current sooner. > > > Sujal >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607110605.XAA12428>