On Saturday 16 September 2006 01:50, mabbas wrote:
I see your point here, although some one will file some bugs against the
driver about showing G while associating with B-mode AP. By the way how
can you figure if the AP is B/G other than the rates?
I don't think this will happen.
This never
with early G AP implementations - so the spec was
changed.
Simon
-Original Message-
From: Michael Wu [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 16, 2006 10:05 AM
To: mabbas
Cc: Simon Barber; netdev@vger.kernel.org
Subject: Re: [d80211] connecting to B-mode AP
On Friday 15
Simon Barber wrote:
Why is it necessary to set phymode to B? - a G client can connect
perfectly well to a B AP.
We need this information for rate scaling and we need to send the NIC
different command depends on the AP connection type.
Mohamed
Simon
-Original Message-
From: [EMAIL
Message-
From: mabbas [mailto:[EMAIL PROTECTED]
Sent: Friday, September 15, 2006 10:19 AM
To: Simon Barber
Cc: netdev@vger.kernel.org
Subject: Re: [d80211] connecting to B-mode AP
Simon Barber wrote:
Why is it necessary to set phymode to B? - a G client can connect
perfectly well to a B AP
, 2006 10:19 AM
To: Simon Barber
Cc: netdev@vger.kernel.org
Subject: Re: [d80211] connecting to B-mode AP
Simon Barber wrote:
Why is it necessary to set phymode to B? - a G client can connect
perfectly well to a B AP.
We need this information for rate scaling and we need to send the NIC
On Friday 15 September 2006 19:50, mabbas wrote:
I see your point here, although some one will file some bugs against the
driver about showing G while associating with B-mode AP. By the way how
can you figure if the AP is B/G other than the rates?
IIRC, only 802.11g APs will send the extended
Why is it necessary to set phymode to B? - a G client can connect
perfectly well to a B AP.
Simon
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of mabbas
Sent: Thursday, September 14, 2006 4:25 PM
To: netdev@vger.kernel.org
Subject: [d80211] connecting
