netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kershaw <dragorn@kismetwireless.net>
To: Jar <jar@pcuf.fi>
Cc: netdev@vger.kernel.org
Subject: Re: Remove Prism II support from Orinoco
Date: Wed, 14 Jun 2006 15:09:03 -0400	[thread overview]
Message-ID: <20060614190903.GB8832@drd1812a> (raw)
In-Reply-To: <448F02F1.3070001@pcuf.fi>

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

On Tue, Jun 13, 2006 at 09:24:49PM +0300, Jar wrote:
> It always loads itself with or without blacklist. That's why I have to 
> do 'rm -f orinoco*.* && depmod -a' when the new kernel arrives. Seems 
> that users are directed to use unsecure orinoco (wep) driver rather than 
> secure hostap (wpa/wpa2,tkip,aes) driver for their prism2 hardware.

The hostap drivers are also much better behaved for rfmon than the
orinoco drivers for prism2.

-m

-- 
Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381  A661 D7B2 8822 738B BDB1

Bus Error at 008BE426 while reading byte from DEADBEEF in User data space


[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-06-14 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 18:24 Remove Prism II support from Orinoco Jar
2006-06-14 19:09 ` Mike Kershaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-10 17:50 [PATCH 2.6.17-rc6] " Faidon Liambotis
2006-06-10 18:08 ` Dave Jones
2006-06-11 22:27   ` Dave Jones
2006-06-11 22:40     ` Dave Jones
2006-06-11 22:49       ` Faidon Liambotis
2006-06-12 15:24         ` John W. Linville
2006-06-13  0:10           ` Jesse Brandeburg
2006-06-13  4:20             ` Stephen Hemminger
2006-06-13  4:30               ` Faidon Liambotis
2006-06-14 11:53                 ` Jiri Benc

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=20060614190903.GB8832@drd1812a \
    --to=dragorn@kismetwireless.net \
    --cc=jar@pcuf.fi \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).