From: Justin Wheeler <jwheeler@datademons.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Giel van Schijndel <me@mortis.eu>
Subject: Patch for f71808e_wdt.c.
Date: Mon, 11 Jun 2012 01:07:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1206110101290.1027@newbox.vps> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 354 bytes --]
Hi,
I have a Jetway JNF99 motherboard, featuring the F71869 SuperIO chip, but its
watchdog chipset ID appears to be 1007 (as opposed to 0814). Some testing
confirmed it behaves the exact same as 0814. The short attached patch adds
that chipset ID to the module's ID list so that the Fintek watchdog driver can
correctly identify and access it.
Justin
[-- Attachment #2: Type: TEXT/PLAIN, Size: 957 bytes --]
--- linux-3.2.12-gentoo.orig/drivers/watchdog/f71808e_wdt.c 2012-06-11 09:48:35.940001076 -0400
+++ linux-3.2.12-gentoo/drivers/watchdog/f71808e_wdt.c 2012-06-11 09:48:35.940001076 -0400
@@ -54,6 +54,7 @@
#define SIO_F71858_ID 0x0507 /* Chipset ID */
#define SIO_F71862_ID 0x0601 /* Chipset ID */
#define SIO_F71869_ID 0x0814 /* Chipset ID */
+#define SIO_F71869A_ID 0x1007 /* Chipset ID */
#define SIO_F71882_ID 0x0541 /* Chipset ID */
#define SIO_F71889_ID 0x0723 /* Chipset ID */
@@ -194,7 +195,7 @@
return -EBUSY;
}
- /* according to the datasheet the key must be send twice! */
+ /* according to the datasheet the key must be sent twice! */
outb(SIO_UNLOCK_KEY, base);
outb(SIO_UNLOCK_KEY, base);
@@ -761,6 +762,7 @@
err = f71862fg_pin_configure(0); /* validate module parameter */
break;
case SIO_F71869_ID:
+ case SIO_F71869A_ID:
watchdog.type = f71869;
break;
case SIO_F71882_ID:
next reply other threads:[~2012-06-11 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 5:07 Justin Wheeler [this message]
2012-06-11 6:20 ` Giel van Schijndel
2012-06-26 18:54 ` Wim Van Sebroeck
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=alpine.DEB.2.00.1206110101290.1027@newbox.vps \
--to=jwheeler@datademons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=me@mortis.eu \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®