OK, when insmod logs "Unknown symbol", is that caused by a specific error return from the kernel module? I'm trying to figure out whether insmod bombs out while inspecting the the module's symbol table (ie. before the driver gets control, in which case we can't do much) or after the driver gets control and fails to initialize with a zero return code, in which case we can print a much more detailed message. (The ppmc driver seems to only give a zero or -1 return code now.) Anybody know?
Thanks, Jon ------------------------------------------------------------------------------ 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
