From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Subject: [PATCH] Allow dependancies of FDDI & Tokenring to be modular.
Date: Fri, 26 Dec 2008 16:52:51 -0500 [thread overview]
Message-ID: <20081226215251.GA5136@redhat.com> (raw)
I noticed it isn't possible to build token ring & fddi drivers
without causing LLC, and a bunch of other things to be forced
built-in. For distro kernels, this means carrying a chunk of
code in the vmlinuz, even if the user doesn't use those protocols.
Signed-off-by: Dave Jones <davej@redhat.com>
--
I don't have any hardware for either of these, so I'm unable to test
if it actually works or not, but seeing as the bits in net/ all have
module_init's, it seems they were meant to be allowed to be built this way.
--- linux-2.6.28.noarch/drivers/net/Kconfig~ 2008-12-25 23:28:55.000000000 -0500
+++ linux-2.6.28.noarch/drivers/net/Kconfig 2008-12-25 23:29:09.000000000 -0500
@@ -2637,7 +2637,7 @@ config RIONET_RX_SIZE
default "128"
config FDDI
- bool "FDDI driver support"
+ tristate "FDDI driver support"
depends on (PCI || EISA || TC)
help
Fiber Distributed Data Interface is a high speed local area network
--- linux-2.6.28.noarch/drivers/net/tokenring/Kconfig~ 2008-12-25 23:54:29.000000000 -0500
+++ linux-2.6.28.noarch/drivers/net/tokenring/Kconfig 2008-12-25 23:54:34.000000000 -0500
@@ -4,7 +4,7 @@
# So far, we only have PCI, ISA, and MCA token ring devices
menuconfig TR
- bool "Token Ring driver support"
+ tristate "Token Ring driver support"
depends on NETDEVICES && !UML
depends on (PCI || ISA || MCA || CCW)
select LLC
--
http://www.codemonkey.org.uk
next reply other threads:[~2008-12-26 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 21:52 Dave Jones [this message]
2008-12-28 4:44 ` [PATCH] Allow dependancies of FDDI & Tokenring to be modular David Miller
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=20081226215251.GA5136@redhat.com \
--to=davej@redhat.com \
--cc=netdev@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.