mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4.19-pre3] New wireless driver API part 1
Date: Wed, 13 Mar 2002 19:19:27 -0800	[thread overview]
Message-ID: <20020313191927.C14095@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020313185915.A14095@bougret.hpl.hp.com> <3C901455.5000704@mandrakesoft.com>
In-Reply-To: <3C901455.5000704@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Mar 13, 2002 at 10:09:09PM -0500

On Wed, Mar 13, 2002 at 10:09:09PM -0500, Jeff Garzik wrote:
> Tangential question, what's up with the prism2 driver?

	Which one ? ;-)
	Orinoco can work sometime with those cards, David may have
some updates in the pipeline (especially for WEP). The Prism2 driver
from Jouni is actually pretty nice and dedicated for those cards.

> It seems like everybody I meet these days has a wireless card which uses 
> the prism2 driver from linux-wlan.org.  And since I just got two of 
> these cards (D-Link DWL-650), I am strongly tempted to merge the driver 
> into the kernel.

	Before doing that, have a chat with Alan that had a close look
with it for a partial opinion. And you may want to go through the
source yourself.
	My personal take is that linux-wlan-ng is nice, does a lot,
but is huge and complex, and it seems that Mark is not that interested
in merging it in the kernel. Keeping it as a separate module may make
most sense.
	BTW, there was a thread about this on the linux-wlan mailing
lists.

> How well does the prism2 driver work with the current wireless driver API?

	Very basic support (mostly read only). linux-wlan-ng has it's
own set of tools and MIB.

> Is there any particular reason why it is not in the kernel now?

	Nobody ever pushed it in. I can't force people to add their
driver int he kernel (hint : compare the list on my web page with the
list in the kernel).

>     Jeff

	Have fun...

	Jean

  reply	other threads:[~2002-03-14  3:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  2:59 Jean Tourrilhes
2002-03-14  3:09 ` Jeff Garzik
2002-03-14  3:19   ` Jean Tourrilhes [this message]
2002-03-14 10:43   ` Bjorn Wesen
2002-03-14 10:49     ` Jeff Garzik
2002-03-15  2:35       ` David Gibson
2002-03-16  0:37         ` Oliver Xymoron
2002-03-14 11:52     ` Wichert Akkerman
2002-03-14  3:20 ` Alan Cox
2002-03-14  3:11   ` Jean Tourrilhes
2002-03-14  3:15     ` Jeff Garzik
2002-03-14  3:25       ` Jean Tourrilhes
2002-03-15  2:43       ` David Gibson
2002-03-15  3:41         ` Jean Tourrilhes
2002-03-14  3:29     ` Alan Cox
2002-03-29  1:08 ` [PATCH 2.4.19-pre4] " 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=20020313191927.C14095@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=jt@hpl.hp.com \
    --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 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®