From: James <bjlockie-ozXLQgHQwDP3fQ9qLvQP4Q@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: identify i2c
Date: Sun, 20 May 2012 16:24:11 -0400 [thread overview]
Message-ID: <4FB952EB.1050505@lockie.ca> (raw)
> # decode-dimms
> # decode-dimms version 5929 (2011-02-16 14:58:38 +0100)
>
> Memory Serial Presence Detect Decoder
> By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,
> Jean Delvare, Trent Piepho and others
> No EEPROM found, are you sure the eeprom module is loaded?
How do I find out what to configure in a 3.4 kernel?
next reply other threads:[~2012-05-20 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 20:24 James [this message]
[not found] ` <4FB952EB.1050505-ozXLQgHQwDP3fQ9qLvQP4Q@public.gmane.org>
2012-05-20 21:00 ` identify i2c Jean Delvare
[not found] ` <20120520230047.45aaa1c0-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-05-20 21:17 ` James
[not found] ` <4FB95F5A.30003-ozXLQgHQwDP3fQ9qLvQP4Q@public.gmane.org>
2012-05-21 5:57 ` Jean Delvare
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=4FB952EB.1050505@lockie.ca \
--to=bjlockie-ozxlqghqwdp3fq9qlvqp4q@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).