From: Peter Hutnick <peter@fpcc.net>
To: John Jasen <jjasen1@umbc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wvlan_cs in limbo?
Date: Mon, 25 Feb 2002 22:31:29 -0700 [thread overview]
Message-ID: <200202260533.WAA30955@perth.fpcc.net> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0202252302120.5307822-100000@irix2.gl.umbc.edu>
In-Reply-To: <Pine.SGI.4.31L.02.0202252302120.5307822-100000@irix2.gl.umbc.edu>
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.
Because linux/Documentation/wavelan.txt says:
"wvlan_cs" driver (Wavelan IEEE, GPL)
-----------------
o Config : Not yet in kernel
o Location : Pcmcia package 3.1.10+
o on-line doc : http://www.fasta.fh-dortmund.de/users/andy/wvlan/
and that page (@fasta.fh-dortmund.de) says:
Download:Kernel 2.0.x / 2.1.x / 2.2.x:
WaveLAN/IEEE Linux driver v1.0.4 (included in pcmcia-cs-3.1.15):
pcmcia-cs-3.1.15.tar.gz
Linux wireless tools v19 (kernel 2.2.13 and earlier):
wireless_tools.19.tar.gz
Linux wireless tools v20 (kernel 2.2.14 and later):
wireless_tools.20.tar.gz
Kernel 2.3.x
Note that kernel 2.3.x support is currently experimental.
WaveLAN/IEEE Linux driver v1.0.4 (patch for kernel 2.3.50):
linux-2.3.50-wvlan.patch.gz
PCMCIA subsystem v3.1.15: pcmcia-cs-3.1.15.tar.gz
Linux wireless tools v20: wireless_tools.20.tar.gz
and
Since the linux kernel 2.4.x contains its own WaveLAN/IEEE 802.11 driver,
this standalone driver is depreciated. Try David Hinds pcmcia package
and/or the linux kernel driver (orinoco_cs).
and orinoco_cs from 2.4.17 doesn't work, but wvlan_cs that came with my RH
kernel does.
but, I checked out the actual pcmcia-cs page, and it looks like I have to
abandon my working PCMCIA stuff, is that right?
I'm open to suggestions. Off list, if you don't mind, being as how I'm off
topic now.
-Peter
next prev parent reply other threads:[~2002-02-26 5:34 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 [this message]
2002-02-28 22:29 ` Jason Cook
2002-03-01 4:01 ` Peter Hutnick
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=200202260533.WAA30955@perth.fpcc.net \
--to=peter@fpcc.net \
--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.