From: Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Identifying i2c devices on Asus P8P67 sandybridge motherboard
Date: Tue, 25 Jan 2011 11:05:20 -0500 [thread overview]
Message-ID: <4D3EF4C0.1090008@cfl.rr.com> (raw)
I recently got a new Asus P8P67 Pro motherboard with a sandybridge core
i5 2500K. After checking the Intel chipset docs, I found that it has an
i2c controller and it was enumerated on the pci bus, but no driver was
loaded for it. I found the i2c-i801 module and the comments in the
source say it supports the Cougar Point (PCH) and matches the PCI ID.
I'm not sure why it wasn't auto loaded, but after loading it, it seemed
to work.
At that point I ran sensors-detect, which failed to recognize any known
controllers on the bus, but i2c-detect found several addresses that
responded. How can I proceed with identifying what these devices are,
so that I can hopefully find or write a driver to communicate with them?
next reply other threads:[~2011-01-25 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 16:05 Phillip Susi [this message]
[not found] ` <4D3EF4C0.1090008-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-25 16:42 ` Identifying i2c devices on Asus P8P67 sandybridge motherboard Jean Delvare
[not found] ` <20110125174246.5061f881-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-25 23:52 ` Phillip Susi
[not found] ` <4D3F622B.9060003-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 8:22 ` Jean Delvare
[not found] ` <20110126092257.7b1243dd-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-26 14:42 ` Phillip Susi
[not found] ` <4D4032CC.5010008-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 20:39 ` Phillip Susi
[not found] ` <4D40866F.4080102-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 21:34 ` Jean Delvare
2011-01-26 21:37 ` 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=4D3EF4C0.1090008@cfl.rr.com \
--to=psusi-3tlf1voikjtqt0dzr+alfa@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