[uClinux-dev] FW: insmod fails with Unknown symbol

[chris brooke]

Thanks for the prompt response.  This is the first time I've heard of restricted and unrestricted symbols.
So to implement option 3 (create a GPL-licensed module that uses the GPL-only symbols and make your
proprietary driver talk through that module)  I can create a GPL module that serves as a wrapper for the
restricted symbols.  My driver would use the wrapper functions exported by that module. 
-- Do I have that right?
Chris

Quoth chris brooke:
> When the module is compiled with a "Proprietary" license insmod fails with

> an unknown symbol:
[...]
> However when the module is compiled with a "Dual BSD/GPL" license there is

> no such problem:
> /mnt/code/gp/module> insmod gp.ko
> gp_init_hw
> /gp_init_hw
> 
> Why is the proprietary license causing the Unknown symbol problem?

Only GPL-licensed modules are allowed to call symbols exported as GPL-only.

> How can I fix it?

Either:

1. modify your module to call unrestricted symbols instead.
2. make your module GPL-licensed instead of proprietary.
3. create a GPL-licensed module that uses the GPL-only symbols and make your
proprietary driver talk through that module.

_________________________________________________________________
Climb to the top of the charts!  Play Star Shuffle:  the word scramble challenge with star power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.uclinux.org/pipermail/uclinux-dev/attachments/20071002/c8a46885/attachment.html