From: Greg KH <greg@kroah.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, frodol@dds.nl, phil@netroedge.com
Subject: Re: 2.5.66: The I2C code ate my grandma...
Date: Fri, 4 Apr 2003 17:14:14 -0800 [thread overview]
Message-ID: <20030405011414.GA5697@kroah.com> (raw)
In-Reply-To: <20030405005950.GA464@zip.com.au>
On Sat, Apr 05, 2003 at 10:59:50AM +1000, CaT wrote:
> On Fri, Apr 04, 2003 at 09:14:24AM -0800, Greg KH wrote:
> > So if you disable the I2C config items, everything works just fine?
>
> Yup.
>
> > I did send out a bugfix for the i2c code for a problem in 2.5.66, it's
> > now included in the latest -bk tree. Could you grab that patch and see
> > if it fixes your problem?
>
> Ok. Running -bk10. Where, umm, is the userspace interface to it? I can't
> find anything in /proc or /sys so I can't see if it's actually working.
> Incase they're useful here are snippets from .config and dmesg:
To a:
tree /sys/bus/i2c/devices/
to see all of the i2c devices in your system.
Then go in to the directories of those devices to see the sensor values
for the devices.
libsensor support will be forthcoming soon for these changes.
> One question. Will I need ISA support in the kernel for this?
Depends, did you need it before? :)
I didn't change any of that logic, just where the information the
sensors report has moved locations.
thanks,
greg k-h
next prev parent reply other threads:[~2003-04-05 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 2:11 2.5.66: The I2C code ate my grandma CaT
2003-04-04 17:14 ` Greg KH
2003-04-05 0:59 ` CaT
2003-04-05 1:14 ` Greg KH [this message]
2003-04-05 1:16 ` CaT
2003-04-05 1:24 ` Greg KH
2003-04-05 1:45 ` CaT
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=20030405011414.GA5697@kroah.com \
--to=greg@kroah.com \
--cc=cat@zip.com.au \
--cc=frodol@dds.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@netroedge.com \
/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