archive mirror
 help / color / mirror / Atom feed
To: Ethan Weinstein <>
Cc: Linux-Kernel <>
Subject: Re: w83627hf watchdog
Date: Mon, 08 Dec 2003 10:33:30 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Ethan Weinstein wrote:
> Hi,
> My Supermicro X5DPL-iGM-O has a winbond w83627hf chip onboard that 
> includes a watchdog timer.  I found a driver on freshmeat that points 
> here:
> but this does not seem to work correctly on 2.4.23, even with my 
> modifications to the ioports and registers that Supermicro sent me. I 
> have tried to contact the developer, he hasn't responded.  I also 
> located a post to linux-kerel quite sometime ago:
>  I haven't tried this driver just yet. The lm_sensors project seems to 
> include a driver for this chip as well, but not for the watchdog part. 
> The specifications Supermicro sent me for the watchdog function are 
> located here:
> Any help would greatly be appreciated, I know this particular chip is 
> included with many motherboards.

That freestone piece of crap didn't work for me,
and looking at the code I'm not surprised.
I did a patch against the existing advantechwdt
since the newer advantechs use the w83627hf.
I think the advantechwdt.c should be renamed to w83627hf_wdt.c
to avoid confusion (or replaced with the w83627hf_wdt.c
you referenced above, that I didn't notice when
I did this).


p.s. I needed to merge the info from a couple
of different winbond manuals to do the driver.
Note also the advantech manual describes the
wrong watchdog!

      parent reply	other threads:[~2003-12-08 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 19:15 w83627hf watchdog Ethan Weinstein
2003-12-05  5:08 ` Ethan Weinstein
2003-12-06 19:59 ` Herbert Poetzl
2003-12-08 10:33 ` P [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).