Hi Wouter,
Thanks for the info,
Regards,
--- On Tue, 14/12/10, Wouter Simons l...@woutersimons.org wrote:
From: Wouter Simons l...@woutersimons.org
Subject: Re: EXPORT_SYMBOL
To: Hemanth Kumar hemw...@yahoo.co.in
Cc: Mulyadi Santosa mulyadi.sant...@gmail.com, Robert P. J
Just to add something from my stupidity land :)
On Tue, Dec 14, 2010 at 13:33, Wouter Simons l...@woutersimons.org wrote:
As for the compiler version, as long as the compiled binaries are
compatible it is possible to use a different GCC version.
Hm, yes...but not really like that :) different
Hi Mulaydi Robert,
Below is the info that is requested,
--- On Sun, 12/12/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
From: Mulyadi Santosa mulyadi.sant...@gmail.com
Subject: Re: EXPORT_SYMBOL
To: Hemanth Kumar hemw...@yahoo.co.in
Cc: Robert P. J. Day rpj
Hi Hemanth.
On Mon, Dec 13, 2010 at 17:05, Hemanth Kumar hemw...@yahoo.co.in wrote:
Hi Mulaydi Robert,
Below is the info that is requested,
OK let's see
--- On Sun, 12/12/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
GCC _
arm-none-linux-gnueabi-gcc
Hi Mulyadi and Robert,
--- On Mon, 13/12/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
From: Mulyadi Santosa mulyadi.sant...@gmail.com
Subject: Re: EXPORT_SYMBOL
To: Hemanth Kumar hemw...@yahoo.co.in
Cc: Robert P. J. Day rpj...@crashcourse.ca, kernelnewbies@nl.linux.org
Date: Monday
On 12/14/2010 06:00 AM, Hemanth Kumar wrote:
Hi Mulyadi and Robert,
[...]
itor disable module versioning entirely...
Thanks for your time and suggestions,I solved this problem,
I added the two modules in kernel dir(driver/misc/),updated
Makefile,Kconfig file
config??
Regards,
--- On Sat, 11/12/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
From: Mulyadi Santosa mulyadi.sant...@gmail.com
Subject: Re: EXPORT_SYMBOL
To: Robert P. J. Day rpj...@crashcourse.ca
Cc: Hemanth Kumar hemw...@yahoo.co.in, kernelnewbies@nl.linux.org
Date: Saturday, 11
Dear Hemanth...
On Sun, Dec 12, 2010 at 18:06, Hemanth Kumar hemw...@yahoo.co.in wrote:
I tried the same idea on this mail,it is not working it is still
giving the same error,
But I tried in CSB667 CSB337 it work's fine not on omap-3630 board,
I am still facing
Hi Mulyadi and Robert,
--- On Sun, 12/12/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
From: Mulyadi Santosa mulyadi.sant...@gmail.com
Subject: Re: EXPORT_SYMBOL
To: Hemanth Kumar hemw...@yahoo.co.in
Cc: Robert P. J. Day rpj...@crashcourse.ca, kernelnewbies@nl.linux.org
Date: Sunday, 12
On Fri, 10 Dec 2010, Hemanth Kumar wrote:
Hi Robert,
The code works well on i386 box kernel-2.6.32.9,but i have
problem on
ARM omap , kernel-2.6.32.9 when I do nm m3.ko it show's ( U rday_3)
cat /proc/kallsyms | grep rday_3
bf011094 D rday_3 [m2]
but when i
On Sat, 11 Dec 2010, Hemanth Kumar wrote:
Hi Robert Mulyadi,
I am using ARM omap-3630 and kernel-2.6.32.9 android froyo
gcc-4.2.1,
dmesg also show's the same message unresolved symbol rday_3,
I have a question does i need tog enable
on this issue will be helpfull.
regards,
hemanth
--- On Sat, 11/12/10, Robert P. J. Day rpj...@crashcourse.ca wrote:
From: Robert P. J. Day rpj...@crashcourse.ca
Subject: Re: EXPORT_SYMBOL
To: Hemanth Kumar hemw...@yahoo.co.in
Cc: kernelnewbies@nl.linux.org
Date: Saturday, 11 December, 2010, 2:01
Hi all...
On Sat, Dec 11, 2010 at 17:03, Robert P. J. Day rpj...@crashcourse.ca wrote:
perhaps mulyadi had the right idea -- that gcc is simply optimizing
that symbol away. add some code to that first module that does
something with that symbol, perhaps prints it, just to make sure gcc
#include linux/module.h
#include linux/init.h
#include linux/kernel.h
static int rday_1 = 1;
int rday_2 = 2;
int rday_3 = 3;
EXPORT_SYMBOL(rday_3);
static int __init hi(void)
{
printk(KERN_INFO module m2 being loaded.\n);
return 0;
}
static void __exit bye(void
= 2;
int rday_3 = 3;
EXPORT_SYMBOL(rday_3);
static int __init hi(void)
{
printk(KERN_INFO module m2 being loaded.\n);
return 0;
}
static void __exit bye(void)
{
printk(KERN_INFO module m2 being unloaded.\n);
}
module_init(hi);
module_exit(bye
this bit strange,Can please share some idea on this.
Regards,
Hemanth
--- On Fri, 10/12/10, Robert P. J. Day rpj...@crashcourse.ca wrote:
From: Robert P. J. Day rpj...@crashcourse.ca
Subject: Re: EXPORT_SYMBOL
To: Hemanth Kumar hemw...@yahoo.co.in
Cc: kernelnewbies@nl.linux.org
Date: Friday, 10
if rday_3 was exported properly, i don't see why it shouldn't be
visible when this module is loaded. anyone else have some thoughts on
this? this clearly worked in the past.
rday
The code looks fine, the only time I ever had similar issues was when I
had my module license
On Fri, 10 Dec 2010, Hemanth Kumar wrote:
Hi Robert,
The code works well on i386 box kernel-2.6.32.9,but i
have problem on ARM omap , kernel-2.6.32.9 when I do nm m3.ko it
show's ( U rday_3)
cat /proc/kallsyms | grep rday_3
bf011094 D rday_3 [m2]
ok, that looks
. So, could you confirm what VM split
your current kernel use?
kernel,Below is the code
file m2.c
#include linux/module.h
#include linux/init.h
#include linux/kernel.h
static int rday_1 = 1;
int rday_2 = 2;
int rday_3 = 3;
EXPORT_SYMBOL(rday_3);
what if we use
in the /proc/kallsyms file?
because EXPORT_SYMBOL doesn't care whether it's eventually exported or
not? just my suspicion..
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
--
To unsubscribe from this list: send
Thanks a lot. It was to do with CONFIG_SPARSE_IRQ. Just overshot my sight.
I had exported a wrong irq_to_desc() which is under the belt of
CONFIG_SPARSE_IRQ which was not configured.
Its working now
Regards,
Prabhu
On Wed, Aug 11, 2010 at 10:34 PM, Mulyadi Santosa mulyadi.sant...@gmail.com
I don't exactly know the problem...but here's something to think...
On Wed, Aug 11, 2010 at 13:07, Prabhu nath gprabhun...@gmail.com wrote:
Hi,
I am facing a peculiar behaviour on Kernel version 2.6.34.1
(http://lxr.linux.no/#linux+v2.6.34.1).
For my experimentation I just
Dear All,
I have written a small sample code for testing the EXPORT_SYMBOL macro
which exports the symbols to the global kernel symbol table. The sample
code is working fine in 2.6.9-1.667 kernel version, however it does not
works fine in 2.6.28 kernel version. I am getting the following errors
I
On Thu, May 7, 2009 at 2:25 PM, Srinivas G.
sriniv...@esntechnologies.co.in wrote:
Dear All,
I have written a small sample code for testing the EXPORT_SYMBOL macro
which exports the symbols to the global kernel symbol table. The sample
code is working fine in 2.6.9-1.667 kernel version
Mulyadi Santosa wrote:
Hm, I got a feeling that you need to try with EXPORT_SYMBOL_GPL
instead.
Dear Santosa,
Thanks for the reply.
I tried with EXPORT_SYMBOL_GPL also. However, there is no much luck and
I got the same error messages.
With Regards,
Srinivas G
--
To unsubscribe from this
PM
Subject: How does EXPORT_SYMBOL work?
Hi,
I am trying to understand how module versioning works in Linux kernel.
If I have a moduleX.ko file with me, how do I determine if it would load
successfully (using insmod or modprobe)? This is purely from versioning
perspective. I assume
the EXPORT_SYMBOL code clearly. It seem to me that it
creates a CRC (somehow) and saves to the kernel symbol table (kallsyms?)
Please clarify to clear my doubt.
Thanks
Durga
\
__attribute__((section(__ksymtab sec), unused)) \
= { (unsigned long)sym, __kstrtab_##sym }
#define EXPORT_SYMBOL(sym) \
__EXPORT_SYMBOL(sym, )
first noticed the extern.so that the symbol
Hi,
How does EXPORT_SYMBOL work ?
All i know is that its a way by which a kernel module can export symbols to
other kernel modules.
Just to get more information on it, i looked for its definition(in
linux/module.h) and found that
its defined as:
#define EXPORT_SYMBOL(sym
Sorry for the typo,
MODULE_VERSION should be read as MODULE_LICENSE.
Thanks,
~amit
On Fri, Dec 5, 2008 at 6:03 PM, amit mehta [EMAIL PROTECTED] wrote:
Hi,
How does EXPORT_SYMBOL work ?
All i know is that its a way by which a kernel module can export symbols to
other kernel modules.
Just
Hi Amit..
On Fri, Dec 5, 2008 at 7:33 PM, amit mehta [EMAIL PROTECTED] wrote:
Hi,
How does EXPORT_SYMBOL work ?
All i know is that its a way by which a kernel module can export symbols to
other kernel modules.
Just to get more information on it, i looked for its definition(in
linux
Hi...
On Sun, Sep 7, 2008 at 5:34 PM, rishi agrawal [EMAIL PROTECTED] wrote:
Hello Everybody,
What is the use of EXPORT_SYMBOL ??
To make it short, by doing that you make that symbol visible to
kernel module. By visible, I mean it can be referenced. Thus if it's
variable you can store a value
Hi Rishi,
rishi agrawal wrote:
Hello Everybody,
What is the use of EXPORT_SYMBOL ??
I found it many a times in the kernel code.
When you want to use a modules functions or variables(symbols) in other
module you have to use the macro.
--
-_-
.
Regards,
R.S.Shree Ram
GDA
pradeep singh wrote:
Hi All,
A Quick but perhaps dumbass query,
1. int function_A(...)
{
...;
}
2. int function_B(...)
{
...;
}
EXPORT_SYMBOL(function_B);
Okay i understand I should use the EXPORT_SYMBOL way if i want
function_B to be used
Hi,
Is it a compulsion for a function which need to be used in any other
source file, exported through EXPORT_SYMBOL only?
Does this means all the places in kernel(and there are loads of
them), where a function is non-static and is used in other source
files should actually be using
EXPORT_SYMBOL macro creates a new kernel symbol entry (address of the symbol,
symbol) based on the value you specify and puts it in a special section of the
kernel image, in __ksymtab section. When modules are loaded dynamically, the
loader resolves the symbols during run time by parsing
Hi All,
A Quick but perhaps dumbass query,
1. int function_A(...)
{
...;
}
2. int function_B(...)
{
...;
}
EXPORT_SYMBOL(function_B);
Okay i understand I should use the EXPORT_SYMBOL way if i want
function_B to be used by rest of the kernel.
Now I have
On Sun, Sep 09, 2007 at 03:23:44PM -0400, Robert P. J. Day wrote:
it occurred to me as i was perusing some of the source files that
some of those files were including module.h for no other reason than
to have access to the EXPORT_* macros. but why are those macros in
module.h?
Because
EXPORT_* macros are used to export the kernel symbols (functions, data
structures) to the outside world viz. modules.
So, these macros are logically tied with the kernel module infrastructure.
Regards,
- Ratnadeep
On 9/10/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
it occurred to me as i
it occurred to me as i was perusing some of the source files that
some of those files were including module.h for no other reason than
to have access to the EXPORT_* macros. but why are those macros in
module.h?
they're not tied specifically to modules. for example, the file
kernel/mutex.c
hi all,
When we export a symbol using EXPORT_SYMBOL, We can use it to be called by
other modules when we insert this module ...
I wanted to know when does this symbol gets added to the kernel symbol table
...
Or what happens when we insert the module so that this symbol is accessible
On Thu, Jul 19, 2007 at 12:05:43AM -0700, kanishk rastogi wrote:
...
But i wanted to see what special treament does these symbols get once we have
EXPORT_SYMBOL()ed them
Vs
ones which are not exported and non static .
The code that does this is in include/linux/module.h
regards
42 matches
Mail list logo
