All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] ASUS P5WD2 Premium - Winbond 83627EHG-A
Date: Fri, 15 Jul 2005 19:48:26 +0000	[thread overview]
Message-ID: <20050715194755.10488fb5.khali@linux-fr.org> (raw)
In-Reply-To: <42D27327.7050402@internode.on.net>

Hi Timothy,

> Yep, I'll have a go at backporting then, mind you, the last time I 
> touched any C code was in a "Hello World" program! haha!  ... So I'll 
> start reading around how to do this, of course any hints/tips would 
> be appreciated (though I recognise your time is important, and I dont 
> expect to be hand-fed).
> 
> I've now downloaded a 22-June-05 build of "w83627ehf.c" (by Greg)
> from GIT (which I dont really get understand)... though not sure
> how/where to complile it yet ... (I'm just wing'n it! haha)

From there, create a Makefile with this line:

obj-m	+= w83627ehf.o

Then run:

make -C /usr/src/linux SUBDIRS=$PWD modules

(replace /usr/src/linux with the path to your real kernel source tree).

That should do it. If there are warnings or errors, you'll have to
figure out how to fix them (or ask us). Then modprobe the new driver and
see how it goes.

> >This should give us the exact ID.
> 
> In the mean time, here's the "isadump" you asked for ... I built this 
> from the CVS version.
> 
> [root@localhost dump]# ./isadump -y -k 0x87,0x87 0x2e 0x2f 0x0b
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: ff ff ff ff ff ff ff 0b ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 20: 88 63 ff 00 44 00 00 ff 50 04 00 00 9a 21 00 ff

For the records, your chip has ID 0x8863, which matches the W83627EHF
datasheet (it says 0x886x), but oddly enough not the ID of the only
W83627EHF chip we saw so far (which had 0x8853). I have good hope that
both chips will be compatible as far as hardware monitoring is
concerned.

Oh, and remember that my w83627ehf driver is not finished, it only
implements half of the features the chip has, due to a lack of time and
hardware to test my work. Someone else is working on improving it. Or I
might do if someone considers a hardware donation.

-- 
Jean Delvare

  parent reply	other threads:[~2005-07-15 19:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 15:55 [lm-sensors] ASUS P5WD2 Premium - Winbond 83627EHG-A Timothy Findlay
2005-07-12 14:50 ` Rudolf Marek
2005-07-13 17:05 ` Timothy Findlay
2005-07-14 13:18 ` Rudolf Marek
2005-07-14 13:25 ` Rudolf Marek
2005-07-15 10:50 ` Timothy Findlay
2005-07-15 11:57 ` Jean Delvare
2005-07-15 18:14 ` Timothy Findlay
2005-07-15 19:48 ` Jean Delvare [this message]
2005-07-17 15:22 ` Timothy Findlay
2005-07-17 17:44 ` Jean Delvare
2005-07-19 17:38 ` Jean Delvare
2005-07-20 14:17 ` Timothy Findlay
2005-07-20 21:14 ` Rudolf Marek
2005-07-24 20:20 ` Jean Delvare
2005-07-25 15:06 ` Carlos Eduardo Medaglia Dyonisio
2005-07-25 20:06 ` 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=20050715194755.10488fb5.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.