linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Fuckner <michael-iWcS09LKDTLR7s880joybQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Decode dimms on dual socket machines
Date: Tue, 12 Apr 2011 14:52:21 +0200	[thread overview]
Message-ID: <4DA44B05.906@fuckner.net> (raw)
In-Reply-To: <20110412132611.045ace21-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>

On 04/12/2011 01:26 PM, Jean Delvare wrote:
Hi all,

> Note that you will need a recent enough kernel (>= 2.6.36) to have
> support for SMBus multiplexing.
currently I use OpenSUSE11.4 with 2.6.37.1-1.2-default


> FWIW, address 0x70 is used by the PCA954x multiplexers, so maybe this
> is what you have (and a driver is available).
>
> At 0x2f is probably a W83793 or W83795 monitoring chip, supported by
> the w83793 and w83795 drivers, respectively. Only use these dedicated
> drivers if you do not intend to use the IPMI features of the board.
>
>> 18,1a,1c: jc42 temperature sensors
>> 50,52,54: eeproms
>


Now I loaded the module

test24:/media/i2c-tools/tools # lsmod |grep pca
pca954x                 3288  0
i2c_mux                 2672  1 pca954x
test24:/media/i2c-tools/tools # ll /sys/bus/i2c/devices/
total 0
lrwxrwxrwx 1 root root 0 Apr 12 14:26 0-0050 -> 
../../../devices/pci0000:00/0000:00:1f.3/i2c-0/0-0050
lrwxrwxrwx 1 root root 0 Apr 12 14:26 0-0052 -> 
../../../devices/pci0000:00/0000:00:1f.3/i2c-0/0-0052
lrwxrwxrwx 1 root root 0 Apr 12 14:26 0-0054 -> 
../../../devices/pci0000:00/0000:00:1f.3/i2c-0/0-0054
lrwxrwxrwx 1 root root 0 Apr 12 13:54 i2c-0 -> 
../../../devices/pci0000:00/0000:00:1f.3/i2c-0

Seems like this is what I need to know, but I don't know how to 
interpret it. Is it multiplexed on the GPIO Pin 52 and 53 at the W83795ADG?

ftp://ftp.supermicro.com/utility/SuperoDoctorINI/AllMEMDIMM.ini

Regards,
  Michael!

  parent reply	other threads:[~2011-04-12 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 10:10 Decode dimms on dual socket machines Michael Fuckner
     [not found] ` <4DA4250A.3060907-iWcS09LKDTLR7s880joybQ@public.gmane.org>
2011-04-12 11:26   ` Jean Delvare
     [not found]     ` <20110412132611.045ace21-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-12 12:52       ` Michael Fuckner [this message]
     [not found]         ` <4DA44B05.906-iWcS09LKDTLR7s880joybQ@public.gmane.org>
2011-04-12 13:53           ` Jean Delvare
     [not found]             ` <20110412155345.4644e51c-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-13  6:13               ` Michael Lawnick
     [not found]                 ` <4DA53F22.5020105-Mmb7MZpHnFY@public.gmane.org>
2011-04-13  8:39                   ` Jean Delvare
     [not found]                     ` <20110413103952.68bdb6fa-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-13 10:06                       ` Michael Fuckner
     [not found]                         ` <4DA575C3.1050100-iWcS09LKDTLR7s880joybQ@public.gmane.org>
2011-04-13 11:45                           ` Jean Delvare
2011-04-19 12:24                           ` Jean Delvare
2011-04-14 11:42                       ` Michael Lawnick

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=4DA44B05.906@fuckner.net \
    --to=michael-iwcs09lkdtlr7s880joybq@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).