That would be a definite step up on what we have now.
	How much extra work would it be to add the locator information
	to the in-kernel decive list, and how would that interact
	with the proposal to have a boot time kernel config interface?


		David/absolute
				       -- www.netbsd.org: No hype required --

On Mon, 5 Jun 2000, Brett Lymn wrote:

> According to Nathan J. Williams:
> >
> >I don't think it should be in the tree. It works by parsing dmesg,
> >which is cheating.
> >
> 
> Well, it does and it does not.  The actual device tree is extracted by
> walking the in-kernel device list.  Only the locator information is
> extracted from dmesg because there was NO OTHER WAY of getting this
> information.  The device structure has some locator information in it
> but that is the config stuff used to find the device and if the device
> was matched on wildcards then those locators will have "-1" in them.
> 
> Prtconf will work quite happily without the information from dmesg but
> just don't expect the locators to be printed.
> 
> -- 
> ===============================================================================
> Brett Lymn, Computer Systems Administrator, BAE SYSTEMS
> ===============================================================================
> 
> 
>