From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
To: linux-kernel@vger.kernel.org
Subject: Re: what happened to i2c-proc
Date: Wed, 28 May 2003 22:29:21 +0200 [thread overview]
Message-ID: <20030528202921.GA8349@localhost> (raw)
In-Reply-To: <m3d6i3avnk.fsf@ccs.covici.com>
On Wednesday, 28 May 2003, at 12:22:23 -0400,
John Covici wrote:
> I am trying to compile appropriate modules for lm sensors in 2.5.70,
> but there seems to be no way to configure i2c-proc -- it seems to be
> there for other architectures, but not for i386.
>
And this is probably the cause of my hardware sensors (it87.ko) not
working :-). Here is what modules.dep for my 2.4.20 kernel says:
/lib/modules/2.4.20-xfsip/kernel/drivers/sensors/it87.o:
/lib/modules/2.4.20-xfsip/kernel/drivers/i2c/i2c-core.o \
/lib/modules/2.4.20-xfsip/kernel/drivers/i2c/i2c-proc.o
And here what it says for my 2.5.70 kernel:
/lib/modules/2.5.70/kernel/drivers/i2c/chips/it87.ko: /lib/modules/2.5.70/kernel/drivers/i2c/i2c-sensor.ko /lib/modules/2.5.70/kernel/drivers/i2c/i2c-core.ko
Or maybe something changed in the meantime, and problems are in
user-space, the fact is it doesn't work:
server:~# sensors -v
sensors version 2.6.5
As seen on lm_sensors' home page, it seems the are still porting i2c and
lm_sensors to recent 2.5.x kernels, so maybe the problem is there. They
advise against trying to compile both i2c and lm_sensors for 2.5.x
kernels, because probably they won't work.
Hope this helps.
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.5.70)
next prev parent reply other threads:[~2003-05-28 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 16:22 what happened to i2c-proc John Covici
2003-05-28 20:29 ` Jose Luis Domingo Lopez [this message]
2003-05-28 23:19 ` Jan Dittmer
2003-05-30 6:26 ` Greg KH
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=20030528202921.GA8349@localhost \
--to=linux-kernel@24x7linux.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.