About EXPORT_SYMBOL

[Sri Ram Vemulpali]

Compiling the kernel should resolve the problem.

EXPORT_SYMBOL_GPL() is more for modules that have GPL license.
So, if you export symbol with GPL license, it is imperative to have GPL
license for modules, accessing that symbol. Otherwise will EXPORT_SYMBOL
it should be fine, to access by any module. In former case, it only
warns at time of
inserting the module for GPL license. Either case you should able to
access the symbol

--Sri.

On Thu, Feb 10, 2011 at 1:04 PM, Dave Hylands <dhylands at gmail.com> wrote:
> Hi Mulyadi,
>
> On Thu, Feb 10, 2011 at 9:22 AM, Mulyadi Santosa
> <mulyadi.santosa at gmail.com> wrote:
>> On Thu, Feb 10, 2011 at 23:23, kashish bhatia <koolest77 at gmail.com> wrote:
>>>
>>> yes I compiled the kernel again and then tried to insert my module. I think
>>> the function is not properly exporting.
>>
>> not sure if it makes difference, but try EXPORT_SYMBOL_GPL() macro
>> instead.... and see if it indeed works...
>
> EXPORT_SYMBOL_GPL is more restrictive than EXPORT_SYMBOL. It only
> allows the symbol to be used by modules which have GPL module
> licesnce.
>
> Kashish, so you know which symbol is unknown?
>
> If you use insmod it should report which symbols are the unknown ones.
> Otherwise you can resort to running nm on your module to see what
> symbols it needs.
>
> Dave Hylands
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 
Regards,
Sri.