Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 01 Jul 2001 14:44:34 +0200
From:      Andre Oppermann <oppermann@monzoon.net>
To:        gerti@BITart.com
Cc:        Andre Oppermann <oppermann@monzoon.net>, freebsd-mobile@freebsd.org
Subject:   Re: Lucent Wavelan and PRISMII
Message-ID:  <3B3F1B32.A25013AE@monzoon.net>
References:  <3B3DEC84.2E357E86@monzoon.net> <20010630230331.6288.qmail@camelot.bitart.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Gerd Knops wrote:
> 
> Andre Oppermann wrote:
> > I have all the information that is needed to make the wi() driver
> > work absolutely cleanly with Lucent Orinoco based and PRISMII based
> > cards.
> >
> > So I am willing to take over the maintainership of the wi() driver
> > and have a patch introducing a lot of additional functionality in
> > approximatly six weeks from now.
> >
> > For my employer I've done the AP functionality into the wi() driver.
> > But that I can't release. I can do any client functionality that is
> > already disclosed in other open-source drivers (which is basically
> > all client functions for Orinoco and PRISMII). Although I have a far
> > better base available than to reengineer those other drivers.
> >
> Maybe you'll be able to clear up the mystery why WEP doesn't work with
> the SMC2632W?

Yes, the WEP configuration RID's have been added independently after
Lucent (WaveLan) and Intersil (Harris) developed the chipset jointly.

So in both API's the RID's are different from each other (not only
that, they also have a different meaning on PRISMII) and if you try
to enable WEP on the PRISMII it'll simply crush the card (at least
my Nokia card is wedged afterwards).

I have documented all differences in both API's and are on the way
of putting the additional code into the driver.

-- 
Andre

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B3F1B32.A25013AE>