We have a driver which (unfortunately) is not open source.
We deliver this driver in binary format (as an rpm) to customers.
Customers sometimes add patches or use newer kernels than what
we compiled with. With versioning (which is default on and *mostly* a
good thing in my opinion) symbol names change and our driver module does
not load. We do not wish to tell our customers to disable versioning.
Is there any way of getting around this?
Our only option at this time seems to be demangling the ksyms
and our module symbols, match them and replace the module symbol
references with the new ones in ksyms (using libbfd or some such).
Not an ideal solution...
What is the "correct" way of doing it? Even with open source kernel
external modules one would like to be able to avoid recompiling them
after doing a minor change in the kernel configuration??
Enlighten me, but please be gentle ;-)
Sincerely
-- Rolf Welde Skeie Senior Design Engineer _____________________________________________________________________ Email : mailto:rws@scali.no Scali AS (http://www.scali.com) Tlf : (+47) 6384 6705 Hvamstubben 17 oo Fax : (+47) 6384 4005 2013 Skjetten __________ m/V\> _ Home : (+47) 2214 8987 NORWAY . . :: . 077-0 Mob : (+47) 9248 4511 ----------------------- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/