From: devik@cdi.cz (Martin Devera)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH 1/1] i2c: add BroadCom HT-1000 to i2c-piix
Date: Wed, 15 Feb 2006 23:42:10 +0000 [thread overview]
Message-ID: <E1F9WHi-0008EA-00@devix> (raw)
From: Martin Devera <devik at cdi.cz>
Add BroadCom HT-1000 south bridge's PCI ID to i2c-piix driver. Note
that at least on Supermicro H8SSL it uses non-standard SMBHSTCFG = 3
and standard values like 0 or 9 causes hangup.
Signed-off-by: Martin Devera <devik at cdi.cz>
---
Kudos to Rudolf Marek for its helpful comments.
diff -ur a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
--- linux-2.6.14.3/drivers/i2c/busses/i2c-piix4.c Tue Feb 14 17:03:23 2006
+++ linux-2.6.15.4/drivers/i2c/busses/i2c-piix4.c Tue Feb 14 16:57:29 2006
@@ -419,6 +419,8 @@
.driver_data = 0 },
{ PCI_DEVICE(PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_CSB6),
.driver_data = 0 },
+ { PCI_DEVICE(PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_HT1000SB),
+ .driver_data = 0 },
{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82443MX_3),
.driver_data = 3 },
{ PCI_DEVICE(PCI_VENDOR_ID_EFAR, PCI_DEVICE_ID_EFAR_SLC90E66_3),
diff -ur a/include/linux/pci_ids.h b/include/linux/pci_ids.h
--- linux-2.6.14.3/include/linux/pci_ids.h Tue Feb 14 17:03:36 2006
+++ linux-2.6.15.4/include/linux/pci_ids.h Tue Feb 14 16:55:16 2006
@@ -1343,6 +1343,7 @@
#define PCI_DEVICE_ID_SERVERWORKS_OSB4 0x0200
#define PCI_DEVICE_ID_SERVERWORKS_CSB5 0x0201
#define PCI_DEVICE_ID_SERVERWORKS_CSB6 0x0203
+#define PCI_DEVICE_ID_SERVERWORKS_HT1000SB 0x0205
#define PCI_DEVICE_ID_SERVERWORKS_OSB4IDE 0x0211
#define PCI_DEVICE_ID_SERVERWORKS_CSB5IDE 0x0212
#define PCI_DEVICE_ID_SERVERWORKS_CSB6IDE 0x0213
next reply other threads:[~2006-02-15 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 23:42 Martin Devera [this message]
2006-02-15 23:47 ` [lm-sensors] [PATCH 1/1] i2c: add BroadCom HT-1000 to i2c-piix Martin Devera
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=E1F9WHi-0008EA-00@devix \
--to=devik@cdi.cz \
--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.