Date: Mon, 23 Oct 1995 20:37:17 +1000 From: Bruce Evans <bde@zeta.org.au> To: hackers@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: New userconfig Message-ID: <199510231037.UAA24992@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>In order to meaninfully interpret the values assigned the basic ISA >device parameters, I currently make the following assumptions : >If a parameter is -1, the driver does not use the parameter. It is never >relevant, and is never consulted. >If a parameter is -2, the driver has a compiled-in default for this parameter, >but the default can be overridden by setting the value to another value. Note that userconfig can't use special values to decide which values can be changed, since it needs to be able to change to and from all values. Currently unadvertised driver capablities determine which values actually make sense. The -1 and -2 above are back to front. -1 has always meant `?' (autoconfig). There is a special rule for this in config/lang.l. Drivers should never use compiled in defaults for this, but they may use values read from firmware. >Joerg has kindly provided details for modifying config(8) to recognise >'auto' and 'none' as alternatives to '?'. I'd like to ask further for >comments (and advice) on setting the _default_ for nonspecified parameters >to 'none' (-1), rather than the currently ambiguous state (some -1, some 0). `none' is a verbose alternative to `'. I think nonspecified parameters always have a value of -1 except in cases where 0 is more natural (for pointers and bitmaps). >Julian, specifically to you, and generally to anyone else working on device >driver registration issues - is there a "better way", that takes advantage >of the devfs concept/support/etc? I think you'll eventually have to modify device tables in 1001 drivers. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510231037.UAA24992>