Andy Pugh wrote: > On 31 August 2010 18:09, Jon Elson<[email protected]> wrote: > >> OK, when insmod logs "Unknown symbol", is that caused by a specific >> error return >> from the kernel module? >> > It seems to me that only the emc2 module knows if it is expecting a > "port_addr=" or a "cfg=" or some other parameter, so the "unknown > symbol" is what insmod ouptuts for the specific error raised by the > emc module? > That's not exactly a true premise. Modules can export symbols (using the EXPORT_SYMBOL macro), and can also specify load-time parameters (for us, using the RTAPI_MP_{INT,STRING,ARRAY ...} macros), which are visible to insmod and the kernel. When you load a module, the kernsl and insmod are responsible for parsing all the values according to the exported symbols and their types. If a parameter is supplied which has no corresponding symbol, then insmod gives that "unknown symbol" error. The kernel or insmod (I don't know exactly how they split the responsibilities) will pre-populate the values in any variables that are recognized on the insmod command line.
- Steve ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
