From: YH <yh@bizmail.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Module link
Date: Sat, 08 Jul 2006 09:34:50 +1000 [thread overview]
Message-ID: <44AEEF9A.4060505@bizmail.com.au> (raw)
In-Reply-To: <17581.63026.514260.403228@hound.rchland.ibm.com>
Thanks for all responses. The file was modified from
drivers/macintosh/therm_adt746x.c, the function call i2c_add_driver() in
static int __init thermostat_init(void) caused a null point. In fact,
all i2c related functions were not linked. The i2c-core.c has been built
in kernel. How does the module therm_adt746x.ko link to i2c? I did not
see that the module therm_adt746x.ko resolved symbol i2c_add_driver. Or,
the symbols are resolved during insmod? I guess I try to figure out
whether this problem is caused by building process in kernel or by
module loading process in insmod (using BusyBox)?
Thank you.
Jim
Dave C Boutcher wrote:
> On Fri, 7 Jul 2006 15:33:43 +1000 (EST), yh@bizmail.com.au said:
>
>>Thanks Randy. Let me clarify it.
>>I have a driver module (NewSerialModule.ko) and I build it for module
>>load. This driver module uses i2c functions. It was fine to init this
>>module in kernel 2.4 as the i2c functions are exported in i2c Makefile.
>>
>>In kernel 2.6, I loaded this module and got NULL point exception. I
>>checked the module map, all i2c functions are not linked. I also checked
>>i2c, there is no export for i2c in kernel 2.6. So, my question is how can
>>I link the dirvers/i2c to my driver module in drivers/char directory? How
>>to export a directory to be a library such as i2c? In general, how to link
>>another directory functions by a module in kernel 2.6?
>
>
> It is difficult for any of us to offer assistance unless you provide a
> pointer to your source code.
>
> However, I will point out that the i2c functions are exported from
> drivers/i2c/i2c-core.c, so you should make sure you have that module
> either built into your kernel or loaded.
>
> Dave B
> -
> 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/
>
prev parent reply other threads:[~2006-07-07 23:34 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
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 [this message]
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=44AEEF9A.4060505@bizmail.com.au \
--to=yh@bizmail.com.au \
--cc=linux-kernel@vger.kernel.org \
/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®