Date: Wed, 6 May 1998 01:20:04 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Mike Smith <mike@smith.net.au>, Archie Cobbs <archie@whistle.com> Cc: stefan@promo.de (Stefan Bethke), luigi@labinfo.iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ISA-PnP w\o BIOS support? Message-ID: <199805060820.BAA20482@salsa.gv.tsc.tdk.com> In-Reply-To: Mike Smith <mike@smith.net.au> "Re: ISA-PnP w\o BIOS support?" (May 5, 11:26pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On May 5, 11:26pm, Mike Smith wrote: } Subject: Re: ISA-PnP w\o BIOS support? } This actually falls a little short. It's easier to look at it from a } different angle, too. } } For each PnP device/function in the system } If the device/function is not supported (unknown, no driver present) } deconfigure device (if required) } continue } else } while resources required } allocate new resources } test resources (using PnP test facility if available) } endwhile } if resources available } allocate a new driver instance, assign resources } else } continue } endif } endfor } } For each explicitly-configured ISA devices } if resource config does not conflict with PnP-configured device } allocate resources } if probe succeeds } allocate new driver instance } else } free resources } endif } endif } endfor Why would you not want to reverse the order and configure the explicitly configured ISA devices first and the PnP devices last? If you configure the PnP devices first, they might use resources required by the ISA devices. If you configure the ISA devices first, then you should be able to adjust the resources used by the PnP devices so they don't conflict with the ISA devices. 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?199805060820.BAA20482>