From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] i2c driver fixes for 2.6.0
Date: Tue, 30 Dec 2003 14:06:15 -0800 [thread overview]
Message-ID: <1072821975626@kroah.com> (raw)
In-Reply-To: <10728219742126@kroah.com>
ChangeSet 1.1496.9.6, 2003/12/04 13:53:39-08:00, khali@linux-fr.org
[PATCH] I2C: add Serverworks CSB6 support to i2c-piix4
This patch adds support for the Serverworks CSB6 to i2c-piix4 driver. It
was confirmed to work by lasirona at yahoo dot com in support ticket
#1424:
http://secure.netroedge.com/~lm78/readticket.cgi?ticket=1424
drivers/i2c/busses/Kconfig | 3 ++-
drivers/i2c/busses/i2c-piix4.c | 9 ++++++++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff -Nru a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
--- a/drivers/i2c/busses/Kconfig Tue Dec 30 12:31:40 2003
+++ b/drivers/i2c/busses/Kconfig Tue Dec 30 12:31:40 2003
@@ -161,11 +161,12 @@
help
If you say yes to this option, support will be included for the Intel
PIIX4 family of mainboard I2C interfaces. Specifically, the following
- versions of the chipset is supported:
+ versions of the chipset are supported:
Intel PIIX4
Intel 440MX
Serverworks OSB4
Serverworks CSB5
+ Serverworks CSB6
SMSC Victory66
This driver can also be built as a module. If so, the module
diff -Nru a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
--- a/drivers/i2c/busses/i2c-piix4.c Tue Dec 30 12:31:40 2003
+++ b/drivers/i2c/busses/i2c-piix4.c Tue Dec 30 12:31:40 2003
@@ -22,7 +22,7 @@
/*
Supports:
Intel PIIX4, 440MX
- Serverworks OSB4, CSB5
+ Serverworks OSB4, CSB5, CSB6
SMSC Victory66
Note: we assume there can only be one device, with one SMBus interface.
@@ -418,6 +418,13 @@
{
.vendor = PCI_VENDOR_ID_SERVERWORKS,
.device = PCI_DEVICE_ID_SERVERWORKS_CSB5,
+ .subvendor = PCI_ANY_ID,
+ .subdevice = PCI_ANY_ID,
+ .driver_data = 0,
+ },
+ {
+ .vendor = PCI_VENDOR_ID_SERVERWORKS,
+ .device = PCI_DEVICE_ID_SERVERWORKS_CSB6,
.subvendor = PCI_ANY_ID,
.subdevice = PCI_ANY_ID,
.driver_data = 0,
next prev parent reply other threads:[~2003-12-30 22:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 22:02 [BK PATCH] i2c driver fixes for 2.6.0 Greg KH
2003-12-30 22:06 ` [PATCH] " Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH [this message]
2003-12-30 22:06 ` Greg KH
2003-12-30 22:06 ` Greg KH
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=1072821975626@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/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