On Mon, Jul 19, 2010 at 1:29 PM, Youngwhan Song breadn...@gmail.com wrote:
I believe the patch should be in the driver code by either changing
names or using of __init_refok rather than modifying of kernel.
Yes, I agree, some change to the driver code,
but which names do I change? variables?,
On Sat, Jul 17, 2010 at 5:41 AM, Mulyadi Santosa
mulyadi.sant...@gmail.com wrote:
Hi Bob..
On Sat, Jul 17, 2010 at 02:08, Bob Beers bob.be...@gmail.com wrote:
Hmmm, It looks lilke a pretty standard Makefile:
---8---
CC=gcc
VER=`uname -r`
On 7/19/10 6:43 AM, Bob Beers wrote:
On Sat, Jul 17, 2010 at 5:41 AM, Mulyadi Santosa
mulyadi.sant...@gmail.com wrote:
Hi Bob..
On Sat, Jul 17, 2010 at 02:08, Bob Beersbob.be...@gmail.com wrote:
Hmmm, It looks lilke a pretty standard Makefile:
On Mon, Jul 19, 2010 at 10:37 AM, Daniel (Youngwhan) Song
breadn...@gmail.com wrote:
I found similar one here:
http://www.mail-archive.com/linux-ker...@vger.kernel.org/msg249131.html
Thanks Daniel,
I'm reading it, but I still haven't seen how to use the warnings to
find/fix the mismatches.
Hi Bob..
On Sat, Jul 17, 2010 at 02:08, Bob Beers bob.be...@gmail.com wrote:
Hmmm, It looks lilke a pretty standard Makefile:
---8---
CC=gcc
VER=`uname -r`
SRCREF?=/lib/modules/$(VER)/build
INSTALLDIR=/lib/modules/$(VER)/kernel/net
It's something like
Hello,
I have read that, These are typically caused by an .text function calling
into .init.text code ie) code that is declared as __init, __devinit, etc..
I am compiling a GPL'd, but not in-kernel, driver and I see several
Section mismatch warnings. And I am seeing kernel panics while
On Fri, Jul 16, 2010 at 2:15 PM, Mulyadi Santosa
mulyadi.sant...@gmail.com wrote:
Hi...
On Fri, Jul 16, 2010 at 21:53, Bob Beers bob.be...@gmail.com wrote:
How do I figure out where to fix it?
Could it be due to custom linker script used in your driver code?
Hmmm, It looks lilke a pretty
