All of lore.kernel.org
 help / color / mirror / Atom feed
From: j.w.r.degoede@hhs.nl (Hans de Goede)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Answer Epox - EPoX EP1308 sensor-chip
Date: Fri, 29 Sep 2006 07:45:07 +0000	[thread overview]
Message-ID: <451CCF03.3060002@hhs.nl> (raw)
In-Reply-To: <450B14DB.2090505@sh.cvut.cz>

Jean Delvare wrote:
>>> Is it still necessary to unlock the superio and if so could to explain why?
>> It looks like its not nescesarry as it works without it.
> 
> Well, if we write a driver for this chip, it's always better to get the
> address from the Super-I/O configuration address space, rather than
> hardcoding an arbitrary address. This lets us detect much more reliably
> whether the device is there or not, and also lets us deal with
> different addresses without user intervention.
> 

Ok,

I'm kinda new to this superio stuff, so I'm glad you and Rudolf are 
helping out.

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.

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?

Also are there datasheets of similar (fintek) superio chips available 
somewhere, those could be of great help.

Regards,

Hans



  parent reply	other threads:[~2006-09-29  7:45 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 [this message]
2006-09-29  7:50 ` Jean Delvare
2006-09-29  8:03 ` Jean Delvare
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=451CCF03.3060002@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --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.