From: Roger Luethi <rl@hellgate.ch>
To: Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH][2.5][Trivial] VIA Rhine Kconfig entry
Date: Sun, 8 Dec 2002 01:34:56 +0100 [thread overview]
Message-ID: <20021208003456.GA12234@k3.hellgate.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Fix and update VIA Rhine description at least for 2.5 (I'll do 2.4, too, if
there's interest). Removed "experimental" flag for Rhine MMIO while I was
at it. Just barely resisted the temptation to make VIA Rhine conflict with
IO-APIC -- that seems to emerge as a fatal combo.
Please apply.
Roger
[-- Attachment #2: Kconfig-via-rhine.diff --]
[-- Type: text/plain, Size: 1441 bytes --]
--- linux-2.5.50/drivers/net/Kconfig.orig Sun Dec 8 00:29:44 2002
+++ linux-2.5.50/drivers/net/Kconfig Sun Dec 8 01:00:40 2002
@@ -1426,8 +1426,10 @@
tristate "VIA Rhine support"
depends on NET_PCI && PCI
help
- If you have a VIA "rhine" based network card (Rhine-I (3043) or
- Rhine-2 (VT86c100A)), say Y here.
+ If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
+ Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
+ Ethernet functions can also be found integrated on South Bridges
+ (e.g. VT8235).
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -1436,15 +1438,15 @@
well as <file:Documentation/networking/net-modules.txt>.
config VIA_RHINE_MMIO
- bool "Use MMIO instead of PIO (EXPERIMENTAL)"
- depends on VIA_RHINE && EXPERIMENTAL
+ bool "Use MMIO instead of PIO"
+ depends on VIA_RHINE
help
This instructs the driver to use PCI shared memory (MMIO) instead of
programmed I/O ports (PIO). Enabling this gives an improvement in
processing time in parts of the driver.
- It is not known if this works reliably on all "rhine" based cards,
- but it has been tested successfully on some DFE-530TX adapters.
+ It is not known if this works reliably on all "Rhine" based cards,
+ but it has been tested successfully on several adapters.
If unsure, say N.
next reply other threads:[~2002-12-08 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 0:34 Roger Luethi [this message]
2002-12-08 3:15 ` Jeff Garzik
2002-12-10 13:28 ` Roger Luethi
2002-12-10 19:19 ` Steve Brueggeman
2002-12-10 20:52 ` Alan Cox
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=20021208003456.GA12234@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=akpm@digeo.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome