From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Answer Epox - EPoX EP1308 sensor-chip
Date: Fri, 29 Sep 2006 08:03:31 +0000 [thread overview]
Message-ID: <20060929100331.652b422e.khali@linux-fr.org> (raw)
In-Reply-To: <450B14DB.2090505@sh.cvut.cz>
Hi Hans,
> Maybe I should make my relation to Hans Edgington clear. As you may know
> I'm a university Computer Science teacher and Hans E. is a student of
> mine. As part of his / her last year every student must work on a
> project for 1 day / week during 5 months. Normally the project
> assignments come from real companies, but when we don't have enough
> assignments the teacher(s) create assignments for these projects. After
> seeing the mail from Age Huisman on this I thought it would be a fun
> project for a student to write a driver for this sensors chip.
Yes, I think this is a good idea, both interesting for the student and
useful for the user waiting for this chip to be supported.
> At first I thought this driver would be much like the uguru driver, but
> I see now with the superio stuff that it will be somewhat different,
> what would be a good driver to start with as a skeleton to base this
> driver on?
There's nothing like the uGuru :p
I'd suggest working off the f71805f driver, as it supports a Fintek
chip so the Super-I/O code should be very similar.
> Also are there datasheets of similar (fintek) superio chips available
> somewhere, those could be of great help.
The Fintek datasheets are unfortunately not publicly available as far
as I know. But Winbond has good datasheets and the Super-I/O mechanism
is pretty standard, so you can start from there (see
Documentation/hwmon/w83627hf for URLs). Or you can simply look at the
f71805f driver code, I would hope it is clear enough.
BTW the Super-I/O mechanism is essentially based on Intel's LPC
specification, which is publicly available here:
http://www.intel.com/design/chipsets/industry/lpc.htm
But it's highly technical and you don't really need to know the details
to write a driver.
Hope that helps,
--
Jean Delvare
next prev parent reply other threads:[~2006-09-29 8:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 21:02 [lm-sensors] Answer Epox - EPoX EP1308 sensor-chip Rudolf Marek
2006-09-28 10:06 ` Hans Edgington
2006-09-28 16:21 ` Hans de Goede
2006-09-28 21:20 ` Rudolf Marek
2006-09-28 21:39 ` Jean Delvare
2006-09-28 21:43 ` Jean Delvare
2006-09-28 23:42 ` Hans Edgington
2006-09-29 7:37 ` Jean Delvare
2006-09-29 7:45 ` Hans de Goede
2006-09-29 7:50 ` Jean Delvare
2006-09-29 8:03 ` Jean Delvare [this message]
2006-09-29 10:32 ` Hans Edgington
2006-09-29 11:27 ` Jean Delvare
2006-10-02 20:46 ` Hans Edgington
2006-10-04 12:08 ` Jean Delvare
2006-10-04 14:01 ` Hans de Goede
2006-10-04 14:43 ` 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=20060929100331.652b422e.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@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.