Hi ,
But the problem with me is that we cannot release the source code.
That's why I am converting my module to test.o in my system itself and
trying to write some shell script to convert it to target test.ko, so
that script is executed in target system my module can be loaded.
Karthik
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Sunday, May 08, 2005 8:13 PM
To: kbuild-devel@lists.sourceforge.net
Subject: kbuild-devel digest, Vol 1 #594 - 4 msgs
Send kbuild-devel mailing list submissions to
kbuild-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kbuild-devel digest..."
Today's Topics:
1. Re: Doubt what is the difference of compiling module in SuSE and
Redhad , Mandrake (Sam Ravnborg)
2. Re: select of non-existing I2C* symbols (Sam Ravnborg)
3. Re: Doubt what is the difference of compiling module in SuSE and
Redhad , Mandrake (Andreas Gruenbacher)
4. Re: select of non-existing I2C* symbols (Russell King)
--__--__--
Message: 1
Date: Sun, 8 May 2005 20:16:59 +0200
From: Sam Ravnborg <[EMAIL PROTECTED]>
To: karthik <[EMAIL PROTECTED]>
Cc: kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Doubt what is the difference of compiling
module in SuSE and Redhad , Mandrake
On Fri, May 06, 2005 at 12:27:12PM -0700, karthik wrote:
> Hi ,
>
> Can anybody tell me what is the difference in compiling a
module in
> SuSE distribution and other LInux distribution like Redhad or
Mandrake.
>
> In 2.6 kernel a module compiled in one version(say 2.6.4) of
SuSE is
> not loading in another version(say 2.6.8) of SuSE, even when we
convert the
> module.o to module.ko in the latest version of SUSE.
Please read Documentation/kbuild/modules.txt
If you follow instructions herein you will no longer:
"convert module.o to module.ko".
And as long as you do wrong stuff like that you are lucky that your
module actually loaded with some kernel version.
Sam
--__--__--
Message: 2
Date: Sun, 8 May 2005 20:20:50 +0200
From: Sam Ravnborg <[EMAIL PROTECTED]>
To: Adrian Bunk <[EMAIL PROTECTED]>
Cc: Jan Dittmer <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
linux-kernel@vger.kernel.org,
kbuild-devel@lists.sourceforge.net,
[EMAIL PROTECTED], sparclinux@vger.kernel.org
Subject: Re: [kbuild-devel] select of non-existing I2C* symbols
> Shouldn't kconfig exit with an error if a not available symbol gets
> selected?
No. There are meny configurations where we select a symbol that is
only visible in some configurations.
Several possibilities exists:
1) Silently ignore SELECT SYMBOL when SYMBOL is undefined
2) Warn - as we do today
3) Error out as you suggest
Option 1) is preferable for 'make oldconfig' simply because target group
here do not care. But it would be nice to know when one do a typing
error in SELECT. So one *config target should continue to warn about it.
Sam
--__--__--
Message: 3
From: Andreas Gruenbacher <[EMAIL PROTECTED]>
To: kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Doubt what is the difference of compiling
module in SuSE and Redhad , Mandrake
Date: Sun, 8 May 2005 21:03:23 +0200
Cc: Sam Ravnborg <[EMAIL PROTECTED]>, karthik <[EMAIL PROTECTED]>
karthik,
On Sunday 08 May 2005 20:16, Sam Ravnborg wrote:
> > In 2.6 kernel a module compiled in one version(say 2.6.4) of
SuSE
> > is not loading in another version(say 2.6.8) of SuSE, even when we
> > convert the module.o to module.ko in the latest version of SUSE.
forget trying to use a 2.6.x module with a 2.6.y kernel where x != y --
it
just won't work, I promise.
-- Andreas.
--__--__--
Message: 4
Date: Sun, 8 May 2005 19:28:59 +0100
From: Russell King <[EMAIL PROTECTED]>
To: Sam Ravnborg <[EMAIL PROTECTED]>
Cc: Adrian Bunk <[EMAIL PROTECTED]>, Jan Dittmer <[EMAIL PROTECTED]>,
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], linux-kernel@vger.kernel.org,
kbuild-devel@lists.sourceforge.net, [EMAIL PROTECTED],
sparclinux@vger.kernel.org
Subject: Re: [kbuild-devel] select of non-existing I2C* symbols
On Sun, May 08, 2005 at 08:20:50PM +0200, Sam Ravnborg wrote:
> > Shouldn't kconfig exit with an error if a not available symbol gets
> > selected?
> No. There are meny configurations where we select a symbol that is
> only visible in some configurations.
>
> Several possibilities exists:
> 1) Silently ignore SELECT SYMBOL when SYMBOL is undefined
> 2) Warn - as we do today
> 3) Error out as you suggest
>
> Option 1) is preferable for 'make oldconfig' simply because target
group
> here do not care. But it would be nice to know when one do a typing
> error in SELECT. So one *config target should continue to warn about
it.
I disagree.
Consider that some developers do not use anything other than "make
oldconfig" so having this silently ignore stuff means that these
folk never get the warnings. I myself fall into this category.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
--__--__--
_______________________________________________
kbuild-devel mailing list
kbuild-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
End of kbuild-devel Digest
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
kbuild-devel mailing list
kbuild-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
