Date: Sat, 4 Jan 1997 17:43:54 +1100 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, jb@cimlogic.com.au Cc: current@FreeBSD.org Subject: Re: MOD_DECL in lkm.h Message-ID: <199701040643.RAA26494@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> Most modules have >> no need for a stat function. > >That's a shame because it is a useful interface for looking at debug info. >Ah well, looks like my module won't have a stat function either. I think most lkm's should have a directly linkable version, so they shouldn't be any special features in the lkm version. You can use a sysctl for debugging (at least when the sysctl() implementation is finished :). >BTW, with lkms, how is device config info (like in kernel config files) >supposed to be passed in rather than hard coding the configuration? I don't think anyone knows. Current drivers have it hard coded :-(. >or IRQs 2 - 7. I'd like to be able to do: > >modload -c config_file -p postinstall XXX_mod.o > >where the config_file might contain something similar to that given to >the kernel config. Then I'd like the number of units to come from the >config_file rather than from the NXXX in the XXX.h header file. How about something like: modload XXX_mod.o XXX_config.o where XXX_config.o is a small object file (something like one line out of ioconf.c compiled to an object)? The config info could be loaded separately but it's not clear how it would be associated with the driver then. I would prefer all drivers (whether lkm's or not) to be dynamically reconfigurable. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701040643.RAA26494>