From: Peter Hutnick <peter@fpcc.net>
To: Jason Cook <jasonc@reinit.org>
Cc: John Jasen <jjasen1@umbc.edu>, linux-kernel@vger.kernel.org
Subject: Re: wvlan_cs in limbo?
Date: Thu, 28 Feb 2002 21:01:29 -0700 [thread overview]
Message-ID: <200202282303.QAA15397@perth.fpcc.net> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0202252302120.5307822-100000@irix2.gl.umbc.edu> <200202260533.WAA30955@perth.fpcc.net> <20020228172958.A10716@panacea.canonical.org>
In-Reply-To: <20020228172958.A10716@panacea.canonical.org>
On Thursday 28 February 2002 03:29 pm, Jason Cook wrote:
> * Peter Hutnick (peter@fpcc.net) wrote:
> > On Monday 25 February 2002 09:03 pm, John Jasen wrote:
> > > On Mon, 25 Feb 2002, Peter Hutnick wrote:
> > > > I can't figure out which end is up with wvlan_cs. Not in the kernel
> > > > yet . . . but pcmcia-cs package is not for use with 2.4.
> > > >
> > > > Could someone give me a hint?
> > >
> > > I don't understand why you think that pcmcia-cs is not for use in 2.4.
> > > I use it on my laptop, which was just recently moved to 2.4.17.
>
> From what I understand the wvlan_cs driver is being phased out and
> replaced by the much improved orinoco_cs driver.
I guess "improved" is somewhat subjective. It doesn't work with my card :-(
The wvlan_cs driver is in the current pcmcia-cs package, but isn't built with
"make all." I'm "just an end user" so I am not really cut out for figuring
out how to build it manually.
Too bad there is no pcmcia-cs mailing list :-(
Guess I'll stick with the working stuff that came with my distro and try the
main tree kernel again around 2.4.21.
-Peter
next prev parent reply other threads:[~2002-02-28 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 3:38 wvlan_cs in limbo? Peter Hutnick
2002-02-26 4:03 ` John Jasen
2002-02-26 5:31 ` Peter Hutnick
2002-02-28 22:29 ` Jason Cook
2002-03-01 4:01 ` Peter Hutnick [this message]
2002-02-28 23:35 ` John Jasen
2002-02-28 21:41 ` Peter Hutnick
2002-03-01 1:01 ` John Jasen
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=200202282303.QAA15397@perth.fpcc.net \
--to=peter@fpcc.net \
--cc=jasonc@reinit.org \
--cc=jjasen1@umbc.edu \
--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 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.