All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: jt@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 orinoco_cs with Lucent WaveLAN "bronze"
Date: Sat, 19 Oct 2002 10:59:38 +0100	[thread overview]
Message-ID: <20021019105938.A14830@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200210190922.g9J9M4p15225@Port.imtp.ilyichevsk.odessa.ua>; from vda@port.imtp.ilyichevsk.odessa.ua on Sat, Oct 19, 2002 at 02:14:57PM +0000

On Sat, Oct 19, 2002 at 02:14:57PM +0000, Denis Vlasenko wrote:
> Today I played with wireless LAN euqipment for the first time.
> I have ISA-to-PCMCIA converter and a Lucent (IEEE) PCMCIA card.
> I set up everything as directed by HOWTOs. I do:

Yes, I also noticed many problems with the current orinoco_cs driver.
I've reported them to David, but had very little response thus far.
Basically, iwconfig ethx essid foo appears to crash the cards firmware
(I get really interesting series of words in the chips registers giving
a nice ASCII string.)

I did find that if I took the wvlan_cs driver from a Red Hat kernel and
drop it into 2.5, it works (as far as I can tell) quite nicely.

Unfortunately, I haven't been able to do any further investigation of
this; I'm not too bothered because wvlan_cs gets me working.

(My card is a Lucent WaveLAN Silver)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-10-19  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 14:14 2.4.19 orinoco_cs with Lucent WaveLAN "bronze" Denis Vlasenko
2002-10-19  9:59 ` Russell King [this message]
2002-10-19 15:02   ` Denis Vlasenko
2002-10-21 17:39   ` Jean Tourrilhes

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=20021019105938.A14830@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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.