mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Mark Watts <m.watts@eris.qinetiq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where Linux 802.11x support needs work
Date: Fri, 28 Jan 2005 12:00:03 -0500	[thread overview]
Message-ID: <1106931603.3051.8.camel@dcbw.boston.redhat.com> (raw)
In-Reply-To: <200501281638.08372.m.watts@eris.qinetiq.com>

On Fri, 2005-01-28 at 16:38 +0000, Mark Watts wrote:
> > o  Firmware issues
> >    1) Cisco aironet firmware upload is quite inconsistent, fails with
> >       5.21 for example.  Firmware <= 5.02 seems to be required for using
> >       WEP with most access points.  Latest Cisco-provided driver is quite
> >       different than latest in-kernel driver
> 
> This might explain why I've never managed to get WEP working with my cisco 
> cards...
> 
> Is there some documentation somewhere on exactly what firmware/driver/kernel 
> versions you need to make WEP work with aironet cards?

Nope.  Cisco-provided drivers (for 2.4-series kernels only) require a
firmware version of 5.30.17.  The in-kernel drivers for the 2.6 series
don't have the updates necessary to work with that version, and it
appears that versions of the firmware that are higher than 5.20.x will
not work for WEP using the in-kernel drivers.

I have personally tried 5.41 and 5.30.17 on a PCMCIA card and found they
do _not_ work with WEP.  I have also tried versions 5.00.01, 5.02.13,
5.00.03, and 5.20.07 (?) on both PCMCIA and MiniPCI cards and found them
to work correctly with WEP-enabled access points.

Dan


      reply	other threads:[~2005-01-28 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 21:47 Dan Williams
2005-01-28 16:38 ` Mark Watts
2005-01-28 17:00   ` Dan Williams [this message]

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=1106931603.3051.8.camel@dcbw.boston.redhat.com \
    --to=dcbw@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@eris.qinetiq.com \
    /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®