From: Francois Romieu <romieu@fr.zoreil.com>
To: netdev@vger.kernel.org
Cc: pascal.chapperon@wanadoo.fr, lars.vahlenberg@mandator.com,
Alexey Dobriyan <adobriyan@gmail.com>,
apatard@mandriva.com, jgarzik@pobox.com, akpm@osdl.org
Subject: [patch 2.6.13-git3 5/5] sis190: basic sis191 support
Date: Sat, 3 Sep 2005 00:57:51 +0200 [thread overview]
Message-ID: <20050902225751.GF25687@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20050902225224.GA25687@electric-eye.fr.zoreil.com>
The sis191 is the gigabit brother of the sis190. SiS's driver suggests
that the register set is backward compatible: this should hopefully
give a basic driver.
The device should allow the usual features from a modern ethernet
adapter (802.1q, SG, Jumbo frames, TSO, checksum offload). So far
the relevant register layout is not documented. SiS's driver does
not provide these features either (at least not for Linux).
Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
diff -puN a/drivers/net/sis190.c~sis190-210 b/drivers/net/sis190.c
--- a/drivers/net/sis190.c~sis190-210 2005-09-02 23:28:05.390587495 +0200
+++ b/drivers/net/sis190.c 2005-09-02 23:28:05.396586525 +0200
@@ -331,14 +331,14 @@ static struct mii_chip_info {
const static struct {
const char *name;
- u8 version; /* depend on docs */
- u32 RxConfigMask; /* clear the bits supported by this chip */
} sis_chip_info[] = {
- { DRV_NAME, 0x00, 0xff7e1880, },
+ { "SiS 190 PCI Fast Ethernet adapter" },
+ { "SiS 191 PCI Gigabit Ethernet adapter" },
};
static struct pci_device_id sis190_pci_tbl[] __devinitdata = {
{ PCI_DEVICE(PCI_VENDOR_ID_SI, 0x0190), 0, 0, 0 },
+ { PCI_DEVICE(PCI_VENDOR_ID_SI, 0x0191), 0, 0, 1 },
{ 0, },
};
diff -puN a/drivers/net/Kconfig~sis190-210 b/drivers/net/Kconfig
--- a/drivers/net/Kconfig~sis190-210 2005-09-02 23:28:05.393587010 +0200
+++ b/drivers/net/Kconfig 2005-09-02 23:28:05.398586202 +0200
@@ -1924,12 +1924,15 @@ config R8169_VLAN
If in doubt, say Y.
config SIS190
- tristate "SiS190 gigabit ethernet support"
+ tristate "SiS190/SiS191 gigabit ethernet support"
depends on PCI
select CRC32
select MII
---help---
- Say Y here if you have a SiS 190 PCI Gigabit Ethernet adapter.
+ Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
+ a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
+ appear in lan on motherboard designs which are based on SiS 965
+ and SiS 966 south bridge.
To compile this driver as a module, choose M here: the module
will be called sis190. This is recommended.
_
prev parent reply other threads:[~2005-09-02 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050902225224.GA25687@electric-eye.fr.zoreil.com>
2005-09-02 22:54 ` [patch 2.6.13-git3 1/5] sis190: unmask the link change events Francois Romieu
2005-09-02 22:55 ` [patch 2.6.13-git3 2/5] sis190: recent chipsets from SiS include a RGMII Francois Romieu
2005-09-02 22:56 ` [patch 2.6.13-git3 3/5] sis190: make 10Mbps the default when handling the StationControl register Francois Romieu
2005-09-02 22:56 ` [patch 2.6.13-git3 4/5] sis190: RGMII Tx internal delay fiddling Francois Romieu
2005-09-02 22:57 ` Francois Romieu [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:
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=20050902225751.GF25687@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=apatard@mandriva.com \
--cc=jgarzik@pobox.com \
--cc=lars.vahlenberg@mandator.com \
--cc=netdev@vger.kernel.org \
--cc=pascal.chapperon@wanadoo.fr \
/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