From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Michael Fuckner <michael-iWcS09LKDTLR7s880joybQ@public.gmane.org>
Cc: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Decode dimms on dual socket machines
Date: Tue, 19 Apr 2011 14:24:37 +0200 [thread overview]
Message-ID: <20110419142437.5eaac154@endymion.delvare> (raw)
In-Reply-To: <4DA575C3.1050100-iWcS09LKDTLR7s880joybQ@public.gmane.org>
Hi Michael,
On Wed, 13 Apr 2011 12:06:59 +0200, Michael Fuckner wrote:
> On 04/13/2011 10:39 AM, Jean Delvare wrote:
>
> >> The challenge will be to detect which of the 8 supported devices (
> >> pca_9540, pca_9542, pca_9543, pca_9544, pca_9545, pca_9546, pca_9547,
> >> pca_9548) is actually to be used.
> >
> > In Michael's case it is irrelevant anyway, as the information he found
> > meanwhile clearly indicates that bus multiplexing is achieved by GPIOs
> > (most certainly on the ICH10) and not an PCA954x chip. The chip at 0x70
> > is probably the Intel 5500 IOH.
>
>
> Supermicro just gave me the following information:
>
> To access all SPDs, you have to pull low GPIO49 (IO_0x528 bit 17) first.
> Then pull low GPIO52 (IO_0x528 bit 20) to access first CPU
> memory(0x50~0x55); pull high GPIO52 to access 2nd CPU memory(0x50~0x55).
>
>
> I can't find anything about GPIO49/52,53 in Datasheet for 5500/5520 chipset
> http://www.intel.com/assets/pdf/datasheet/321328.pdf
>
> So it is probably connected to ICH10
> http://www.intel.com/Assets/PDF/datasheet/319973.pdf
>
> but I don't know how to use this information
I've written a kernel driver to gain access to the GPIO pins of the
ICH10 (and previous ICH chips too.) It's available here:
http://khali.linux-fr.org/devel/misc/i801_gpio/
Generic instructions for standalone drivers are here:
http://khali.linux-fr.org/devel/misc/INSTALL
I would appreciate if you could give it a try on your system and report
everything in the kernel log after loading the driver. By default it
won't change the GPIO values so it should be totally safe.
Thanks,
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
next prev parent reply other threads:[~2011-04-19 12:24 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
[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 [this message]
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=20110419142437.5eaac154@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael-iWcS09LKDTLR7s880joybQ@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@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).