All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jar <jar@pcuf.fi>
To: netdev@vger.kernel.org
Subject: Re: [PATCH 1/5] new pcmcia IDs for hostap - ASUS WL-110
Date: Sat, 13 May 2006 13:43:53 +0300	[thread overview]
Message-ID: <4465B869.3020801@pcuf.fi> (raw)

Pavel Roskin wrote:
 >I strongly believe that every driver should list all devices it can
 >support.  In case of multiple drivers supporting one device, the choice
 >should be done in userspace.

Just from end user's standpoint:

I am totally bored with this "model". Every time new kernel comes I 
first delete all orinoco drivers, because I can't even blacklist them. I 
don't want to use them, I have a better driver -->hostap. When I try to 
do the following in the /etc/modprobe.d/blacklist-custom :

# a) Do NOT load orinoco_pci/plx when we are using hostap driver
# b) Do NOT load eepro100, 8139cp

blacklist orinoco_pci
blacklist orinoco_plx

blacklist eepro100
blacklist 8139cp

The eepro100 and 8139cp get blacklisted just fine but not the 
orinoco_pci, it always want to load itself.

Because of this and the lack of WPA support in orinoco drivers the 
prism2 id:s should be removed from the orinoco drivers. To achieve 
security you have to run vpn over wireless when you use orinoco drivers.

How the orinoco driver can be as _good_ as the hostap driver for the 
prism2 cards? I think hostap is a lot better.

-- 
Best Regards, Jar

             reply	other threads:[~2006-05-13 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 10:43 Jar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12 16:57 [PATCH 1/5] new pcmcia IDs for hostap - ASUS WL-110 Jean Tourrilhes
2006-05-12 17:04 ` Marcin Juszkiewicz
2006-05-12 20:17 ` Pavel Roskin
2006-05-23 15:40 ` Olivier Blin
2006-05-12 13:21 Marcin Juszkiewicz
2006-05-12 20:44 ` Pavel Roskin
2006-05-13  9:58 ` Jochen Friedrich

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=4465B869.3020801@pcuf.fi \
    --to=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 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.