From: Andrew Morton <andrewm@uow.edu.au>
To: David Hinds <dhinds@sonic.net>
Cc: Miles Lane <miles@megapathdsl.net>,
Aaron Eppert <eppertan@rose-hulman.edu>,
dhinds@zen.stanford.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 Patch for 3c575
Date: Thu, 11 Jan 2001 22:55:38 +1100 [thread overview]
Message-ID: <3A5D9F3A.FCC82709@uow.edu.au> (raw)
In-Reply-To: <20010110204420.A7699@rose-hulman.edu> <3A5D20D6.6090906@megapathdsl.net>, <3A5D20D6.6090906@megapathdsl.net>; from Miles Lane on Wed, Jan 10, 2001 at 06:56:22PM -0800 <20010110201537.F12593@sonic.net>
David Hinds wrote:
>
> On Wed, Jan 10, 2001 at 06:56:22PM -0800, Miles Lane wrote:
> >
> > There's one other annoyance:
> >
> > The config files for pcmcia-cs expect the 3c575_cb driver,
> > so I either have to hack the configuration files or load
> > the 3c59x driver by hand.
>
> Yes, I'm not sure how to best communicate the fact that 3c59x should
> be used to cardmgr.
mm.. An `alias 3c575_cb 3c59x' in modules.conf works, but
screws things up when you boot back into 2.2. Alternative
is to go into the modules directory and symlink 3c575_cb->3c59x
The other problem is that in 2.4 cardmgr isn't told the
name of the interface which was bound to the newly-inserted NIC.
I don't know why more people aren't getting bitten by this
with pcmcia-cs+2.4.
I have a rude patch against the pcmcia-cs scripts at
http://www.uow.edu.au/~andrewm/linux/3c59x-2.3-changelog.txt
which works around this.
-
-
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:[~2001-01-11 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 1:44 2.4.0 Patch for 3c575 Aaron Eppert
2001-01-11 2:56 ` Miles Lane
2001-01-11 4:15 ` David Hinds
2001-01-11 7:21 ` Miles Lane
2001-01-11 7:56 ` David Hinds
2001-01-11 11:55 ` Andrew Morton [this message]
2001-01-11 17:26 ` David Hinds
2001-01-11 7:32 ` Miles Lane
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=3A5D9F3A.FCC82709@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=dhinds@sonic.net \
--cc=dhinds@zen.stanford.edu \
--cc=eppertan@rose-hulman.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
/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