public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, frodol@dds.nl, phil@netroedge.com
Subject: Re: 2.5.66: The I2C code ate my grandma...
Date: Sat, 5 Apr 2003 11:16:07 +1000	[thread overview]
Message-ID: <20030405011607.GB464@zip.com.au> (raw)
In-Reply-To: <20030405011414.GA5697@kroah.com>

On Fri, Apr 04, 2003 at 05:14:14PM -0800, Greg KH wrote:
> 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.

AHA! I was sure I ran find /sys -name '*i2c*'. hrrumph.

> libsensor support will be forthcoming soon for these changes.

Cool. I'll just modify my little script for now. :)

> > One question. Will I need ISA support in the kernel for this?
> 
> Depends, did you need it before?  :)

No. But it made me wonder. :)

> I didn't change any of that logic, just where the information the
> sensors report has moved locations.

Well so far so good. Haven't stressed it yet. Wanted to see that i2c was
actually functioning first. :)

-- 
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
	- http://www.informationclearinghouse.info/article2479.htm

  reply	other threads:[~2003-04-05  1:05 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
2003-04-05  1:16       ` CaT [this message]
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=20030405011607.GB464@zip.com.au \
    --to=cat@zip.com.au \
    --cc=frodol@dds.nl \
    --cc=greg@kroah.com \
    --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