From: Pavel Roskin <proski@gnu.org>
To: Faidon Liambotis <paravoid@debian.org>
Cc: linux-wireless@vger.kernel.org, hermes@gibson.dropbear.id.au,
Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH 2.6.23 3/3] [wireless] orinoco: create a Kconfig option for Prism2
Date: Wed, 25 Jul 2007 01:30:20 -0400 [thread overview]
Message-ID: <1185341420.12322.44.camel@dv> (raw)
In-Reply-To: <46A5269F.5050504@debian.org>
On Tue, 2007-07-24 at 01:07 +0300, Faidon Liambotis wrote:
> [I'm adding Jouni to Cc to help us :)]
>
> OK.
> I merely compared the PCI IDs. If you're right, hostap claims that it
> can support devices it can't. We should remove these...
The problem is identifying those IDs, which can require a lot of work.
Direct testing would require hardware that's very hard to get.
> To be honest, I can't imagine people actively working on either of the
> two drivers. The hardware isn't being sold anymore and the technology
> (.11b) is two generations behind. And it's not like the drivers aren't
> working.
> OTOH, I'm not watching closely, so may be I'm far off. You know better :)
Actually, there is some activity on adding volatile firmware download
support for Agere cards and WPA support in Orinoco. There is also a
driver for Orinoco USB devices in the Orinoco subversion repository,
which will be hopefully merged some day.
I'm working on several other drivers, and I'm already overstretched, but
I hope to get back to Orinoco once I can get some other drivers into a
good shape.
> So, I'll sent, if you agree, a patch that only disables orinoco_pci and
> the PCMCIA IDs. If you know more (a specific ID of a PLX that can
> definitely work with hostap) please say so.
I'm sorry, but considering your original patch, I just cannot be sure
that you will get the PCMCIA IDs right. I cannot be sure I'll get it
right myself. It requires a lot of searching and detective work.
> I'll let Jouni comment on the Agere and Symbol rip from hostap.
>
> As for the other solutions, I have none of good knowledge of the
> drivers, time or motivation for something like that.
>
> I think we should find a solution for now and leave the big plans for
> when/if they happen.
The problem is that proper ID classification may be harder than the
handover. I realize that it's still not trivial.
On the other hand, I haven't heard many complains about the ID clash
recently. It seems to me that users learned how to deal with it.
Distributions do a great job too. For instance, Fedora renames network
devices based on the MAC addresses, so the same configuration will work
with either orinoco of hostap.
Of course, those who want to run an 802.11b AP know that they should
choose hostap, but most users don't need that.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-07-25 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 13:17 [PATCH 2.6.23 3/3] [wireless] orinoco: create a Kconfig option for Prism2 Faidon Liambotis
2007-07-22 17:14 ` Pavel Roskin
2007-07-23 22:07 ` Faidon Liambotis
2007-07-25 5:30 ` Pavel Roskin [this message]
2007-07-25 6:19 ` Faidon Liambotis
2007-07-25 16:32 ` Pavel Roskin
2007-08-01 3:33 ` Jouni Malinen
2007-08-01 5:55 ` Pavel Roskin
2007-07-23 1:42 ` David Gibson
2007-07-23 6:10 ` Pavel Roskin
2007-07-23 6:20 ` David Gibson
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=1185341420.12322.44.camel@dv \
--to=proski@gnu.org \
--cc=hermes@gibson.dropbear.id.au \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=paravoid@debian.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).