Date: Tue, 24 Oct 1995 00:51:31 +1000 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, msmith@atrad.adelaide.edu.au Cc: hackers@freebsd.org Subject: Re: New userconfig Message-ID: <199510231451.AAA04819@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> 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. >Given that the driver parameters are unadvertised, special values have to be >used, unless you care to suggest an alternative form of telepathy. Given that there are no special values, sysconfig can't refuse to change any value. It must be possible to change from the "can't change" value to any value without dropping back to the command line userconfig (BTW, visuserconfig() always clears the screen and returns 1 so that it is impossible to drop back to the command line or see what you were doing if you could). >> Drivers should never use compiled in defaults for this, but they may use >> values read from firmware. >Some drivers, as has already been established, need to use compiled-in >defaults in order to function usefully in this imperfect world 8( They should be fixed. >Is anything specific going to break if nonspecified parameters become -2, >rather than -1? Probably not. grep 'iobase == ' in isa/*.c shows only a test against IOBASEUNK in NetBSD (?) code in aic6360.c. grep 'iobase <' shows some bogus insensitive tests in asc.c, gsc.c and lpt.c. These tests once broken when id_iobase was changed to an unsigned type like it should be. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510231451.AAA04819>