Date: Thu, 11 Sep 1997 15:46:47 +1000 From: Mike Smith <mike@smith.net.au> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: Mike Smith <mike@smith.net.au>, Eivind Eklund <perhaps@yes.no>, freebsd-hackers@freebsd.org Subject: Re: PnP support Message-ID: <199709110546.PAA06738@word.smith.net.au> In-Reply-To: Your message of "Wed, 10 Sep 1997 23:10:15 MST." <19970910231015.01243@hydrogen.nike.efn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Mike Smith scribbled this message on Sep 11: > > > > > > well... actually.. this won't be neccessary soon.. I plan on adding > > > resource registering to the pnp code soon... once this is done, the > > > isa probe code should automaticly skip over this... > > > > Please, if you are going to do this, go back to the discussion that > > came up last time on this topic, most particularly the allocation and > > attachment strategy that Stefan and I discussed. Doing this job > > half-assed is just going to mean that it will have to be done again. > > Do it right and people will love you forever. > > are you talking about making auto resource assignment?? if you are, > that wasn't what I was refering too... I mean go back and read the discussion that came up last time "how to integrate PnP" was raised. Right now it's arriving via feeping creaturism, which is OK in that it gives us functionality that we didn't have, but it's basically Wrong, and gives us momentum in the wrong direction. If you have the time to do this, *please* take a little more of it to do it right. We've been over all this several times, and have hashed out some pretty good models. Doug Rabson got a long way through completely redesigning the ISA driver model with huge advantages before disappearing. Don't just throw all this work away. Please? > currently the PnP code DOES NOT claim that a device is using port space > (i.e. to prevent conflics) or memory space for that mater... this is > what I was talking about... not automaticly assigned free resources... If you want a decent resource/extent manager, have a look at the NetBSD extent manager. Whilst Jason may disagree, a little work would see it fitting _very_ well into the picture when it comes to carving up space, and we do need it very much. mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709110546.PAA06738>