From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: yh@bizmail.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module link
Date: Thu, 6 Jul 2006 21:08:05 -0700 [thread overview]
Message-ID: <20060706210805.b9e952ca.rdunlap@xenotime.net> (raw)
In-Reply-To: <3306.58.105.227.226.1152244539.squirrel@58.105.227.226>
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
next prev parent reply other threads:[~2006-07-07 4:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 3:55 yh
2006-07-07 4:08 ` Randy.Dunlap [this message]
2006-07-07 5:33 ` yh
2006-07-07 5:49 ` Arjan van de Ven
2006-07-07 5:50 ` Dave C Boutcher
2006-07-07 23:34 ` YH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060706210805.b9e952ca.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yh@bizmail.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®