All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Greg KH <greg@kroah.com>
Cc: CaT <cat@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.68-bk7: Where oh where have my sensors gone? (i2c)
Date: Mon, 05 May 2003 15:34:55 -0400	[thread overview]
Message-ID: <3EB6BCDF.2020300@wmich.edu> (raw)
In-Reply-To: <20030505182648.GA1826@kroah.com>


Ok, then the sensors program that is part of the lm_sensors package is 
just not up to date with the drivers since it complains about no 
i2c-proc and has no options for looking at sysfs.

My via686a sensors seem to be working just fine in .69


Greg KH wrote:
> On Mon, May 05, 2003 at 02:14:25PM -0400, Ed Sweetman wrote:
> 
>>hey guys.  Notice a missing proc driver? hint: i2c.    That's why 
>>sensors wont work even when you load the modules. At least that's what i 
>>can tell from what the lm_sensors page mentions and what not.
> 
> 
> Huh?
> The i2c code now interacts to userspace through sysfs, not /proc
> anymore.  CaT is properly looking for his sensors in sysfs.
> 
> Here's what happens when looking through sysfs on my box running 2.5.69:
> 
> # find /sys/ | grep -i i2c
> /sys/bus/i2c
> /sys/bus/i2c/drivers
> /sys/bus/i2c/drivers/lm75
> /sys/bus/i2c/drivers/lm75/0-0048
> /sys/bus/i2c/devices
> /sys/bus/i2c/devices/0-0048
> /sys/devices/pci0/00:1f.3/i2c-0
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_input
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_min
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_max
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/power
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/name
> /sys/devices/pci0/00:1f.3/i2c-0/power
> /sys/devices/pci0/00:1f.3/i2c-0/name
> 
> Which is what should be showing up on CaT's machine (of the lm75 device
> is on his hardware.)
> 
> Hope this helps,
> 
> greg k-h
> -
> 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/
> 



  reply	other threads:[~2003-05-05 19:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27 11:56 2.5.68-bk7: Where oh where have my sensors gone? (i2c) CaT
2003-04-28 20:55 ` Greg KH
2003-05-05  8:34   ` CaT
2003-05-05  9:04     ` CaT
2003-05-05 16:58     ` Greg KH
2003-05-05 18:14       ` Ed Sweetman
2003-05-05 18:26         ` Greg KH
2003-05-05 19:34           ` Ed Sweetman [this message]
2003-05-05 20:39             ` Greg KH
2003-05-06  9:00               ` Wade
2003-05-06 16:30                 ` Greg KH
2003-05-06  3:26           ` 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=3EB6BCDF.2020300@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=cat@zip.com.au \
    --cc=greg@kroah.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.