lkml.org 
[lkml]   [2006]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Module link
On Fri, 7 Jul 2006 13:55:39 +1000 (EST) yh@bizmail.com.au wrote:

> Thanks for all helps. The module can now be loaded. There are some other
> issues as descripbled as follows:
>
> 1. The module I used links to i2c drivers. It works fine in kernel 2.4
> after "insmod NewModule.o", but now it has a NULL point in kernel 2.6 when
> to init it. It seems that the i2c driver is not linked in the module. How
> can I link an i2c to my driver module?

Sorry, I don't understand the question.
Where is the driver source code?

> 2. In kernel 2.4, when I call "insmod NewModule.o", the insmod can find
> the path of the NewModule.o and to init the module. In 2.6 kernel, the
> "insmod NewModule.ko" does not know the path, so I have to specify the
> path explicitly as "insmod
> /lib/modules/2.6.8.1/kernel/drivers/char/NewModule.ko" to make it work. I
> guess the above problem in question 1 may also related to this issue. What
> did I wrong here?

In module-init-tools, insmod requires full path and modprobe
does not (it searches for the file).

---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-07-07 06:09    [W:0.074 / U:0.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site