From: David Hinds <dhinds@lahmed.stanford.edu>
To: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
Cc: Tobias Ringstrom <tori@tellus.mine.nu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why not PCMCIA built-in and yenta/i82365 as modules
Date: Tue, 21 Nov 2000 17:50:11 -0800 [thread overview]
Message-ID: <20001121175011.C18265@lahmed.stanford.edu> (raw)
In-Reply-To: <dhinds@lahmed.stanford.edu> <200011220144.eAM1iUf08680@sleipnir.valparaiso.cl>
In-Reply-To: <200011220144.eAM1iUf08680@sleipnir.valparaiso.cl>; from vonbrand@sleipnir.valparaiso.cl on Tue, Nov 21, 2000 at 10:44:30PM -0300
On Tue, Nov 21, 2000 at 10:44:30PM -0300, Horst von Brand wrote:
>
> If you have a laptop with an assortment of cards, you might want to have
> the generic builtin and the cards themselves as modules.
No, that's ok, and that's supported with the current config scripts.
The original question was about having the generic code built in, but
the socket driver (yenta) as a module. The socket driver needs to be
loaded regardless of what cards you're using. So I think having one
in the kernel and the other as a module is of limited utility.
-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-22 2:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 22:34 Tobias Ringstrom
2000-11-22 0:04 ` David Hinds
2000-11-22 1:10 ` Albert D. Cahalan
2000-11-22 1:28 ` David Hinds
2000-11-22 1:44 ` Horst von Brand
2000-11-22 1:50 ` David Hinds [this message]
2000-11-22 10:54 ` Tobias Ringstrom
2000-11-22 10:25 ` Matti Aarnio
2000-11-22 12:29 ` Alan Cox
2000-11-24 17:06 ` Oliver Xymoron
2000-11-22 11:05 ` David Woodhouse
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=20001121175011.C18265@lahmed.stanford.edu \
--to=dhinds@lahmed.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
--cc=vonbrand@sleipnir.valparaiso.cl \
/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
all inboxes | Powered by JetHome®