* Re: 2.6.35-rc5+ WARNING at net/mac80211/scan.c:262
From: Dominik Brodowski @ 2010-07-26 8:17 UTC (permalink / raw)
To: Johannes Berg; +Cc: ilw, linux-wireless
In-Reply-To: <1279873990.3745.1.camel@jlt3.sipsolutions.net>
Hey,
On Fri, Jul 23, 2010 at 10:33:10AM +0200, Johannes Berg wrote:
> > > Oh, it's against wireless-testing, which apparently has some other mods
> > > there. I'll have to see if any other patch needs to go into .35 too.
> >
> > That's fine, I'll just test wireless-testing plus your patch from now on ;)
>
> Hah, ok, I made a note to backport the patch for you, guess I'll delete
> it. Wouldn't have gotten around to it today anyway I think.
the problem didn't reappear when using wireless-testing plus your patch. As
I can't reproduce it -- it just happened every once in a while (maybe once a
day?) -- this doesn't necessarily mean the bug is fixed, but...
Best,
Dominik
^ permalink raw reply
* Re: 2.6.35-rc5+ WARNING at net/mac80211/scan.c:262
From: Johannes Berg @ 2010-07-26 8:21 UTC (permalink / raw)
To: Dominik Brodowski; +Cc: ilw, linux-wireless
In-Reply-To: <20100726081713.GA14192@comet.dominikbrodowski.net>
On Mon, 2010-07-26 at 10:17 +0200, Dominik Brodowski wrote:
> Hey,
>
> On Fri, Jul 23, 2010 at 10:33:10AM +0200, Johannes Berg wrote:
> > > > Oh, it's against wireless-testing, which apparently has some other mods
> > > > there. I'll have to see if any other patch needs to go into .35 too.
> > >
> > > That's fine, I'll just test wireless-testing plus your patch from now on ;)
> >
> > Hah, ok, I made a note to backport the patch for you, guess I'll delete
> > it. Wouldn't have gotten around to it today anyway I think.
>
> the problem didn't reappear when using wireless-testing plus your patch. As
> I can't reproduce it -- it just happened every once in a while (maybe once a
> day?) -- this doesn't necessarily mean the bug is fixed, but...
Alright, thanks. I don't suppose you tried wireless-testing w/o the
patch?
johannes
^ permalink raw reply
* Re: 2.6.35-rc5+ WARNING at net/mac80211/scan.c:262
From: Dominik Brodowski @ 2010-07-26 8:27 UTC (permalink / raw)
To: Johannes Berg; +Cc: ilw, linux-wireless
In-Reply-To: <1280132498.3693.2.camel@jlt3.sipsolutions.net>
On Mon, Jul 26, 2010 at 10:21:38AM +0200, Johannes Berg wrote:
> On Mon, 2010-07-26 at 10:17 +0200, Dominik Brodowski wrote:
> > Hey,
> >
> > On Fri, Jul 23, 2010 at 10:33:10AM +0200, Johannes Berg wrote:
> > > > > Oh, it's against wireless-testing, which apparently has some other mods
> > > > > there. I'll have to see if any other patch needs to go into .35 too.
> > > >
> > > > That's fine, I'll just test wireless-testing plus your patch from now on ;)
> > >
> > > Hah, ok, I made a note to backport the patch for you, guess I'll delete
> > > it. Wouldn't have gotten around to it today anyway I think.
> >
> > the problem didn't reappear when using wireless-testing plus your patch. As
> > I can't reproduce it -- it just happened every once in a while (maybe once a
> > day?) -- this doesn't necessarily mean the bug is fixed, but...
>
> Alright, thanks. I don't suppose you tried wireless-testing w/o the
> patch?
No. Shall I?
Best,
Dominik
^ permalink raw reply
* Re: 2.6.35-rc5+ WARNING at net/mac80211/scan.c:262
From: Johannes Berg @ 2010-07-26 8:32 UTC (permalink / raw)
To: Dominik Brodowski; +Cc: ilw, linux-wireless
In-Reply-To: <20100726082754.GA14881@comet.dominikbrodowski.net>
On Mon, 2010-07-26 at 10:27 +0200, Dominik Brodowski wrote:
> > > the problem didn't reappear when using wireless-testing plus your patch. As
> > > I can't reproduce it -- it just happened every once in a while (maybe once a
> > > day?) -- this doesn't necessarily mean the bug is fixed, but...
> >
> > Alright, thanks. I don't suppose you tried wireless-testing w/o the
> > patch?
>
> No. Shall I?
Well, I'd be interested in whether or not my patch fixed it, but I think
I'll push it upstream anyway.
johannes
^ permalink raw reply
* Re: iwlwifi connection problems
From: Johannes Berg @ 2010-07-26 9:17 UTC (permalink / raw)
To: Guy, Wey-Yi; +Cc: Alex Romosan, linux-wireless@vger.kernel.org
In-Reply-To: <1279917523.10769.1.camel@wwguy-huron>
On Fri, 2010-07-23 at 13:38 -0700, Guy, Wey-Yi wrote:
> Hi Johannes,
>
> On Fri, 2010-07-23 at 13:14 -0700, Alex Romosan wrote:
> > since kernel 2.6.35-rc3 (i didn't try 1 or 2) i haven't been able to
> > connect to a hidden wireless access point using the iwlwifi driver. i
> > can connect to open ones though (the ones that broadcast their name).
> > 2.6.34 worked without any problems. any ideas?
> >
> > this is with the driver in the standard linux kernel (2.6.35-rc6 is the
> > latest one i tried).
>
> Do you aware any changes?
Nope, and it works fine here on wireless-testing.
johannes
^ permalink raw reply
* iw dev wlan0 link - "Not connected"
From: Zhongliang Zhao @ 2010-07-26 9:29 UTC (permalink / raw)
To: linux-wireless
Dear all,
When I use "iw dev wlan0 link" to get information on wlan0 (basically to
check the channel used on wlan0),
it says: " Not connected "
Can someone tell me how to fix this?
Many thanks.
Zhongliang Zhao
^ permalink raw reply
* Hardware needs to know when EAP nego is complete
From: Juuso Oikarinen @ 2010-07-26 11:06 UTC (permalink / raw)
To: johannes, linux-wireless; +Cc: Coelho Luciano Roth
Hello Johannes, hello all,
As you may know the wl1271 hardware implements WLAN-Bluetooth
co-existence by toggling a single antenna between WLAN and Bluetooth.
To pull this off, several quirks are required, for instance WLAN must be
forced to full-PSM so that antenna-time for BT can be made available.
This is implemented by the wl1271 driver with the help of the mac80211.
There are lots of timing issues involved, and there is a priority
between WLAN an BT. To ensure BT A2DP and SCO work properly, BT needs to
have enough priority at the expense of WLAN performance. While this
works well enough when connected, during WLAN association and especially
during EAP negotiation the priority needs to be more on the WLAN side to
ensure reliability.
The wl1271 driver starts association with the priority on WLAN, which
means that BT performance is compromised. The wl1271 driver should
change the priority to BT after association and the EAP negotiations are
complete, to make sure BT is performing acceptably.
So, what this all boils down to is that the wl1271 driver needs to know
when the association, including the possible EAP negotations are fully
complete, to be able to adjust the priority.
Currently, there is no such information available to the driver. In fact
this information is not available anywhere in the kernel level either
(as the details of the EAP negotiation, needed keys etc are controlled
in user-space), so the trigger would need to come from user-space.
To enable this, an operand would be needed to nl80211 to indicate
completion of association (including the EAP negotiations.)
Corresponding functions would then be needed on the cfg80211 ops and
mac80211 ops.
User-space would then call the operand when association is complete. For
open/WEP AP's the operand would be called immediately after association,
and for WPA AP's the operand would be called once the EAP negotiations
are complete.
Thoughts? Ideas? Would this be acceptable?
-Juuso
^ permalink raw reply
* Re: Hardware needs to know when EAP nego is complete
From: Johannes Berg @ 2010-07-26 11:23 UTC (permalink / raw)
To: Juuso Oikarinen; +Cc: linux-wireless, Coelho Luciano Roth
In-Reply-To: <1280142400.6475.33.camel@wimaxnb.nmp.nokia.com>
On Mon, 2010-07-26 at 14:06 +0300, Juuso Oikarinen wrote:
> Hello Johannes, hello all,
>
> As you may know the wl1271 hardware implements WLAN-Bluetooth
> co-existence by toggling a single antenna between WLAN and Bluetooth.
>
> To pull this off, several quirks are required, for instance WLAN must be
> forced to full-PSM so that antenna-time for BT can be made available.
> This is implemented by the wl1271 driver with the help of the mac80211.
>
> There are lots of timing issues involved, and there is a priority
> between WLAN an BT. To ensure BT A2DP and SCO work properly, BT needs to
> have enough priority at the expense of WLAN performance. While this
> works well enough when connected, during WLAN association and especially
> during EAP negotiation the priority needs to be more on the WLAN side to
> ensure reliability.
>
> The wl1271 driver starts association with the priority on WLAN, which
> means that BT performance is compromised. The wl1271 driver should
> change the priority to BT after association and the EAP negotiations are
> complete, to make sure BT is performing acceptably.
>
> So, what this all boils down to is that the wl1271 driver needs to know
> when the association, including the possible EAP negotations are fully
> complete, to be able to adjust the priority.
>
> Currently, there is no such information available to the driver. In fact
> this information is not available anywhere in the kernel level either
> (as the details of the EAP negotiation, needed keys etc are controlled
> in user-space), so the trigger would need to come from user-space.
>
> To enable this, an operand would be needed to nl80211 to indicate
> completion of association (including the EAP negotiations.)
> Corresponding functions would then be needed on the cfg80211 ops and
> mac80211 ops.
>
> User-space would then call the operand when association is complete. For
> open/WEP AP's the operand would be called immediately after association,
> and for WPA AP's the operand would be called once the EAP negotiations
> are complete.
>
>
> Thoughts? Ideas? Would this be acceptable?
I really don't like this. You _can_ figure out if a given frame is EAP
by looking at its ethertype (but don't implement WAPI then!) ... can't
you just give it priority _by frame_?
Also, it doesn't make any sense, since if you really care then you want
rekeying to also have priority...
johannes
^ permalink raw reply
* Re: Hardware needs to know when EAP nego is complete
From: Juuso Oikarinen @ 2010-07-26 11:42 UTC (permalink / raw)
To: ext Johannes Berg
Cc: linux-wireless@vger.kernel.org,
Coelho Luciano (Nokia-MS/Helsinki)
In-Reply-To: <1280143430.3693.7.camel@jlt3.sipsolutions.net>
On Mon, 2010-07-26 at 13:23 +0200, ext Johannes Berg wrote:
> On Mon, 2010-07-26 at 14:06 +0300, Juuso Oikarinen wrote:
> >
> >
> > Thoughts? Ideas? Would this be acceptable?
>
> I really don't like this. You _can_ figure out if a given frame is EAP
> by looking at its ethertype (but don't implement WAPI then!) ... can't
> you just give it priority _by frame_?
I don't like it either, but my hands are bound. With this chip I cannot
give priority by frame. The way it works on that chip is that after
association you tell the chip to change mode, and that's it - no going
back.
> Also, it doesn't make any sense, since if you really care then you want
> rekeying to also have priority...
Yep, this is a problem I too have been thinking about. However, with
this chip, you cannot change the priority back for re-keying. So
essentially, those negotiations are done with the "lowered" WLAN
priority, and if they happen to fail the connection manager will as
result end up associating again with increased priority.
The fact is we need this to be done this way. I have been thinking about
all possible ways to do this hack inside the driver, triggering on
setting of keys etc, but as far as I can tell it's not doable without
assumptions having unacceptable impact on functionality.
We'll have to consider some driver-specific hack-interface then, along
with a correspondingly hacked user-space connection manager. This will
just cause other users of the wl1271 driver ending up with dysfunctional
BT-WLAN coex.
-Juuso
> johannes
>
^ permalink raw reply
* Re: [PATCH] mac80211: simplify key locking
From: Jouni Malinen @ 2010-07-26 14:20 UTC (permalink / raw)
To: Johannes Berg; +Cc: John Linville, linux-wireless
In-Reply-To: <1280130178.3693.1.camel@jlt3.sipsolutions.net>
On Mon, Jul 26, 2010 at 09:42:58AM +0200, Johannes Berg wrote:
> On Sun, 2010-07-25 at 18:39 -0700, Jouni Malinen wrote:
> > - ieee80211_key_disable_hw_accel(key);
> > + if (key->local)
> > + ieee80211_key_disable_hw_accel(key);
>
>
> > - ieee80211_debugfs_key_remove(key);
> > + if (key->local)
> > + ieee80211_debugfs_key_remove(key);
>
> These might look odd, but they're fine on a key that hasn't been used
> since it couldn't have been uploaded to hardware, or put into debugfs,
> so they'll just exit right away.
Well, the latter one may indeed do that since debugfs_remove_recursive()
survives NULL pointer. However, the former one does not.
ieee80211_key_disable_hw_accel() has a key->local dereference and it
oopses without the "if (key->local)" part here (before checking whether
the key is uploaded to hardware). I started first making that handle
unlinked keys, but since this gets called before
ieee80211_key_enable_hw_accel() in the problem case, it looked more
logical to fix the caller not to get to the disable function in the
first place.
--
Jouni Malinen PGP id EFC895FA
^ permalink raw reply
* Re: [PATCH] mac80211: simplify key locking
From: Johannes Berg @ 2010-07-26 14:27 UTC (permalink / raw)
To: Jouni Malinen; +Cc: John Linville, linux-wireless
In-Reply-To: <20100726142058.GA7324@jm.kir.nu>
On Mon, 2010-07-26 at 07:20 -0700, Jouni Malinen wrote:
> Well, the latter one may indeed do that since debugfs_remove_recursive()
> survives NULL pointer. However, the former one does not.
> ieee80211_key_disable_hw_accel() has a key->local dereference and it
> oopses without the "if (key->local)" part here (before checking whether
> the key is uploaded to hardware). I started first making that handle
> unlinked keys, but since this gets called before
> ieee80211_key_enable_hw_accel() in the problem case, it looked more
> logical to fix the caller not to get to the disable function in the
> first place.
Oh, indeed, that comes before the check. I agree then, this patch seems
like the best fix.
johannes
^ permalink raw reply
* Re: Hardware needs to know when EAP nego is complete
From: Jouni Malinen @ 2010-07-26 14:30 UTC (permalink / raw)
To: Juuso Oikarinen; +Cc: johannes, linux-wireless, Coelho Luciano Roth
In-Reply-To: <1280142400.6475.33.camel@wimaxnb.nmp.nokia.com>
On Mon, Jul 26, 2010 at 02:06:40PM +0300, Juuso Oikarinen wrote:
> There are lots of timing issues involved, and there is a priority
> between WLAN an BT. To ensure BT A2DP and SCO work properly, BT needs to
> have enough priority at the expense of WLAN performance. While this
> works well enough when connected, during WLAN association and especially
> during EAP negotiation the priority needs to be more on the WLAN side to
> ensure reliability.
Could you please explain why EAP negotiation is a special case? It is
using data frames just like any other operation after it..
> So, what this all boils down to is that the wl1271 driver needs to know
> when the association, including the possible EAP negotations are fully
> complete, to be able to adjust the priority.
This sounds like a horrible hack and really, the unreliability during
EAP should likely fixed in some other way.
> Currently, there is no such information available to the driver. In fact
> this information is not available anywhere in the kernel level either
> (as the details of the EAP negotiation, needed keys etc are controlled
> in user-space), so the trigger would need to come from user-space.
That's not actually true.. At least when run with wpa_supplicant is
setting operation state to IF_OPER_UP when the full authentication
sequence (i.e., not only EAP, but also the following 4-way handshake
with EAPOL-Key frames) is done (and IF_OPER_DORMANT when not ready).
This is needed for other purposes to indicate when real data traffic can
be sent, e.g., for DHCP clients.
I don't think I would support the idea of using that information to
change the WLAN vs. BT priority without some additional data on what
exactly goes wrong during EAP negotiation, but at least the information
should already be in the kernel, so we do not need to change nl80211 for
this.
--
Jouni Malinen PGP id EFC895FA
^ permalink raw reply
* Re: [PATCH] ath5k: disable ASPM
From: Maxim Levitsky @ 2010-07-26 16:34 UTC (permalink / raw)
To: Jussi Kivilinna; +Cc: ath5k-devel, linux-wireless, Luis R. Rodriguez
In-Reply-To: <20100528100901.14580.1322.stgit@fate.lan>
Hi,
Just want to summarize and finally put that problem to rest.
Was the patch that removes & sets on CONFIG_PCIEASPM? accepted?
Is it possible to check that all ath5k pcie devices that must not use
L0s actually have the 'PCI_EXP_DEVCAP_RBER' disabled (this bit causes
pcie device be marked as legacy, and ASPM is disabled on it)
Best regards,
Maxim Levitsky
^ permalink raw reply
* Re: BUG at arch/x86/mm/physaddr.c:5
From: Luis R. Rodriguez @ 2010-07-26 16:55 UTC (permalink / raw)
To: Jike Song
Cc: Ortwin Glück, linux-kernel, Felix Fietkau,
Vasanthakumar Thiagarajan, jmalinen, Sujith.Manoharan,
senthilkumar, linux-wireless
In-Reply-To: <AANLkTikrmM0pwBLLMWTCO-stRnoCxwQf0M3ZByc7=8_b@mail.gmail.com>
2010/7/25 Jike Song <albcamus@gmail.com>:
> 2010/7/23 Ortwin Glück <odi@odi.ch>:
>> On 23.07.2010 10:04, Jike Song wrote:
>>> Seems to be a logical error? Does the following patch remove your Oops?
>>
>> Looking at the init code I agree. Yes, the patch fixes the OOPS. I am sure
>> because the OOPS occurred at every boot and now it's gone.
>>
>> Thanks!
>>
>> Ortwin
>
> Hi Maintainers,
>
> Since Ortwin has confirmed this patch , would you give me an ACK/NAK please?
>
>
> --
> Thanks,
> Jike
>
>
> From 1414829dcc5b53ef4802f5de2b9be58e2ca0fb23 Mon Sep 17 00:00:00 2001
> From: Jike Song <albcamus@gmail.com>
> Date: Mon, 26 Jul 2010 13:42:41 +0800
> Subject: [PATCH] ath9k: fix wrong DMA direction in RX tasklet
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit
>
> Commit b5c80475abaad015699384ca64ef8229fdd88758 introduced edma
> support for RX, hence bidirectional DMA support. But it
> specified the DMA type as DMA_FROM_DEVICE by mistake.
>
> Reported-and-tested-by: Ortwin Glück <odi@odi.ch>
> Signed-off-by: Jike Song <albcamus@gmail.com>
> ---
> drivers/net/wireless/ath/ath9k/recv.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/recv.c
> b/drivers/net/wireless/ath/ath9k/recv.c
> index ca6065b..e3e5291 100644
> --- a/drivers/net/wireless/ath/ath9k/recv.c
> +++ b/drivers/net/wireless/ath/ath9k/recv.c
> @@ -844,9 +844,9 @@ int ath_rx_tasklet(struct ath_softc *sc, int flush, bool hp)
> int dma_type;
>
> if (edma)
> - dma_type = DMA_FROM_DEVICE;
> - else
> dma_type = DMA_BIDIRECTIONAL;
> + else
> + dma_type = DMA_FROM_DEVICE;
>
> qtype = hp ? ATH9K_RX_QUEUE_HP : ATH9K_RX_QUEUE_LP;
> spin_lock_bh(&sc->rx.rxbuflock);
> --
I'll let Felix chime in on this one as he last reviewed this path.
There were some serious issues with MIPs and DMA that at this point I
think only he grocked.
Luis
^ permalink raw reply
* [RFC] ath9k: improve aggregation throughput by using only first rate
From: Björn Smedman @ 2010-07-26 17:10 UTC (permalink / raw)
To: ath9k-devel, linux-wireless
Hi all,
I've been running a lot of iperf on AR913x /
compat-wireless-2010-07-16 (w/ openwrt/trunk@22388).
I think there are some (in theory) simple improvements that can be
done to the tx aggregation / rate control logic. A proof of concept of
one such improvement is provided below. Basically, it's a hack that
makes ath9k output aggregates with only the first rate in the rate
series. The reasoning is that a failure is not a problem for
aggregates because there is software retry. Retrying in hardware at a
slower rate is counter productive. So, better to fail and do a
software retry at possibly another rate. Also, since the aggregate
size is often limited by the slowest rate in the MRR series (4 ms txop
limit) having a slow rate in the series may affect performance even if
it is never used by the hardware.
In my (not so scientific) tests max AP downstream throughput increases
about 30-40% with the patch below (from 33.9 to 55.7 Mbit/s with HT20
in noisy environment with 20 meters and a few walls between AP and
client).
Of course, if all rates in the series are high then this patch has no effect.
/Björn
---
diff -urpN a/drivers/net/wireless/ath/ath9k/xmit.c
b/drivers/net/wireless/ath/ath9k/xmit.c
--- a/drivers/net/wireless/ath/ath9k/xmit.c 2010-07-26 15:35:17.000000000 +0200
+++ b/drivers/net/wireless/ath/ath9k/xmit.c 2010-07-26 17:11:33.000000000 +0200
@@ -565,7 +565,7 @@ static u32 ath_lookup_rate(struct ath_so
*/
max_4ms_framelen = ATH_AMPDU_LIMIT_MAX;
- for (i = 0; i < 4; i++) {
+ for (i = 0; i < 1; i++) {
if (rates[i].count) {
int modeidx;
if (!(rates[i].flags & IEEE80211_TX_RC_MCS)) {
@@ -1553,6 +1553,9 @@ static void ath_buf_set_rate(struct ath_
if (sc->sc_flags & SC_OP_PREAMBLE_SHORT)
ctsrate |= rate->hw_value_short;
+ if (bf_isaggr(bf))
+ rates[1].count = rates[2].count = rates[3].count = 0;
+
for (i = 0; i < 4; i++) {
bool is_40, is_sgi, is_sp;
int phy;
^ permalink raw reply
* Re: BUG at arch/x86/mm/physaddr.c:5
From: Felix Fietkau @ 2010-07-26 17:22 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: Jike Song, Ortwin Glück, linux-kernel,
Vasanthakumar Thiagarajan, jmalinen, Sujith.Manoharan,
senthilkumar, linux-wireless, John W. Linville
In-Reply-To: <AANLkTi=Ga2Sy60=wXKQT3nv_PRYw-og7279bD9LTWENE@mail.gmail.com>
On 2010-07-26 6:55 PM, Luis R. Rodriguez wrote:
> 2010/7/25 Jike Song <albcamus@gmail.com>:
>> 2010/7/23 Ortwin Glück <odi@odi.ch>:
>>> On 23.07.2010 10:04, Jike Song wrote:
>>>> Seems to be a logical error? Does the following patch remove your Oops?
>>>
>>> Looking at the init code I agree. Yes, the patch fixes the OOPS. I am sure
>>> because the OOPS occurred at every boot and now it's gone.
>>>
>>> Thanks!
>>>
>>> Ortwin
>>
>> Hi Maintainers,
>>
>> Since Ortwin has confirmed this patch , would you give me an ACK/NAK please?
>>
> I'll let Felix chime in on this one as he last reviewed this path.
> There were some serious issues with MIPs and DMA that at this point I
> think only he grocked.
A patch exactly like that was already posted and merged into the
wireless-testing tree a while ago, it apparently just hasn't made it to
Linus' tree. John, could we get this one into 2.6.35?
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=56824223ac97ca845652c59bed9ce139e100261b
commit 56824223ac97ca845652c59bed9ce139e100261b
Author: Ming Lei <tom.leiming@gmail.com>
Date: Fri May 14 21:15:38 2010 +0800
ath9k: fix dma direction for map/unmap in ath_rx_tasklet
For edma, we should use DMA_BIDIRECTIONAL, or else use
DMA_FROM_DEVICE.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
^ permalink raw reply
* Re: iw dev wlan0 link - "Not connected"
From: Luis R. Rodriguez @ 2010-07-26 17:23 UTC (permalink / raw)
To: Zhongliang Zhao; +Cc: linux-wireless
In-Reply-To: <4C4D5560.2040201@iam.unibe.ch>
On Mon, Jul 26, 2010 at 2:29 AM, Zhongliang Zhao <zhao@iam.unibe.ch> wrote:
> Dear all,
>
> When I use "iw dev wlan0 link" to get information on wlan0 (basically to
> check the channel used on wlan0),
> it says: " Not connected "
>
> Can someone tell me how to fix this?
Refer to:
http://wireless.kernel.org/en/users/Documentation/iw#Getting_link_status
And then:
http://wireless.kernel.org/en/users/Documentation/iw#Establishing_a_basic_connection
What you really want to use is:
http://wireless.kernel.org/en/users/Documentation/wpa_supplicant
Luis
^ permalink raw reply
* linux-wireless compile broken
From: Ben Greear @ 2010-07-26 17:31 UTC (permalink / raw)
To: linux-wireless
Pulled and attempted to build linux-wireless this morning:
[greearb@build-32 linux-wireless.p4s]$ make bzImage modules
make -C /home/greearb/git/wireless-2.6 O=/home/greearb/kernel/2.6/linux-wireless.p4s/. bzImage modules
Using /home/greearb/git/wireless-2.6 as source for kernel
GEN /home/greearb/kernel/2.6/linux-wireless.p4s/Makefile
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL /home/greearb/git/wireless-2.6/scripts/checksyscalls.sh
CHK include/generated/compile.h
LD drivers/staging/built-in.o
CC [M] drivers/staging/netwave/netwave_cs.o
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:250: error: expected specifier-qualifier-list before ‘dev_node_t’
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c: In function ‘netwave_snapshot’:
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:291: error: ‘netwave_private’ has no member named ‘lastExec’
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:302: error: implicit declaration of function ‘copy_from_pc’
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:302: error: ‘netwave_private’ has no member named ‘nss’
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c: In function ‘netwave_get_wireless_stats’:
/home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:318: error: ‘netwave_private’ has no member named ‘ramBase’
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply
* Re: [ath9k-devel] [RFC] ath9k: improve aggregation throughput by using only first rate
From: Felix Fietkau @ 2010-07-26 17:44 UTC (permalink / raw)
To: Björn Smedman; +Cc: ath9k-devel, linux-wireless
In-Reply-To: <AANLkTimWoSTAtb0m9V=0CNowhy=KtpiKj-O3vdmV8qxB@mail.gmail.com>
On 2010-07-26 7:10 PM, Björn Smedman wrote:
> Hi all,
>
> I've been running a lot of iperf on AR913x /
> compat-wireless-2010-07-16 (w/ openwrt/trunk@22388).
>
> I think there are some (in theory) simple improvements that can be
> done to the tx aggregation / rate control logic. A proof of concept of
> one such improvement is provided below. Basically, it's a hack that
> makes ath9k output aggregates with only the first rate in the rate
> series. The reasoning is that a failure is not a problem for
> aggregates because there is software retry. Retrying in hardware at a
> slower rate is counter productive. So, better to fail and do a
> software retry at possibly another rate. Also, since the aggregate
> size is often limited by the slowest rate in the MRR series (4 ms txop
> limit) having a slow rate in the series may affect performance even if
> it is never used by the hardware.
>
> In my (not so scientific) tests max AP downstream throughput increases
> about 30-40% with the patch below (from 33.9 to 55.7 Mbit/s with HT20
> in noisy environment with 20 meters and a few walls between AP and
> client).
>
> Of course, if all rates in the series are high then this patch has no effect.
I think it makes sense to rely less on on-chip MRR for fallback, but I
think to make this workable, we really should use the MRR table for
something, otherwise the rate control algorithm will take much longer to
adapt.
It's probably better to fix this properly after I'm done with my A-MPDU
rewrite, because then I can more easily push parts of the software
retransmission behaviour into minstrel_ht directly.
- Felix
^ permalink raw reply
* Re: linux-wireless compile broken
From: John W. Linville @ 2010-07-26 17:49 UTC (permalink / raw)
To: Ben Greear; +Cc: linux-wireless
In-Reply-To: <4C4DC659.7090006@candelatech.com>
On Mon, Jul 26, 2010 at 10:31:05AM -0700, Ben Greear wrote:
> Pulled and attempted to build linux-wireless this morning:
>
> [greearb@build-32 linux-wireless.p4s]$ make bzImage modules
> make -C /home/greearb/git/wireless-2.6 O=/home/greearb/kernel/2.6/linux-wireless.p4s/. bzImage modules
> Using /home/greearb/git/wireless-2.6 as source for kernel
> GEN /home/greearb/kernel/2.6/linux-wireless.p4s/Makefile
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CALL /home/greearb/git/wireless-2.6/scripts/checksyscalls.sh
> CHK include/generated/compile.h
> LD drivers/staging/built-in.o
> CC [M] drivers/staging/netwave/netwave_cs.o
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:250: error: expected specifier-qualifier-list before ‘dev_node_t’
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c: In function ‘netwave_snapshot’:
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:291: error: ‘netwave_private’ has no member named ‘lastExec’
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:302: error: implicit declaration of function ‘copy_from_pc’
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:302: error: ‘netwave_private’ has no member named ‘nss’
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c: In function ‘netwave_get_wireless_stats’:
> /home/greearb/git/wireless-2.6/drivers/staging/netwave/netwave_cs.c:318: error: ‘netwave_private’ has no member named ‘ramBase’
wireless-2.6 doesn't have this:
commit e5b3e80016198ee55c82dfd653c1dee99a38964b
Author: Greg Kroah-Hartman <gregkh@suse.de>
Date: Wed May 5 23:17:29 2010 -0700
Staging: netwave: delete the driver
It has sat in the staging directory since October of 2009, and no one
has stepped up to take it over, so odds are, no one cares about it
anymore. So, it is now deleted as scheduled, and documented in the TODO
file.
Cc: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
You should probably just turn-off that driver in your .config.
Anyway, I normally recommend that people use wireless-testing for
actual development.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: linux-wireless compile broken
From: Ben Greear @ 2010-07-26 18:01 UTC (permalink / raw)
To: John W. Linville; +Cc: linux-wireless
In-Reply-To: <20100726174902.GD3903@tuxdriver.com>
On 07/26/2010 10:49 AM, John W. Linville wrote:
> On Mon, Jul 26, 2010 at 10:31:05AM -0700, Ben Greear wrote:
> Cc: John W. Linville<linville@tuxdriver.com>
> Signed-off-by: Greg Kroah-Hartman<gregkh@suse.de>
>
> You should probably just turn-off that driver in your .config.
> Anyway, I normally recommend that people use wireless-testing for
> actual development.
Ok, I'll dig up wireless-testing.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply
* Re: Atheros 0cf3:b003
From: Luis R. Rodriguez @ 2010-07-26 18:29 UTC (permalink / raw)
To: sergi; +Cc: linux-wireless
In-Reply-To: <loom.20100724T095719-176@post.gmane.org>
On Sat, Jul 24, 2010 at 1:04 AM, sergi <sergitfe1974@gmail.com> wrote:
> Luis R. Rodriguez <mcgrof@...> writes:
>
>>
>> 2010/7/23 Maximi89 <maximi89@...>:
>> > Hola Luis, conoces ese ID?, Atheros 0cf3:b003
>> > Es efectivamente un AR9271?
>>
>> No, cual tarjeta es esa? Las que tenemos son estos:
>>
>
>> { },
>> };
>>
>> Stephen, have you heard of 0cf3:b003 as an ar9271 or HB94 card?
>>
>> Luis
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@...
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>> Hola Luis yo fui quien le mando la consulta a maximiliano,,mi lapiz usb es de
> la casa Ubiquiti modelo wifistation ext y ahi dicen k tiene el atheros 9271..y
> el id k me sale es el mencionado,,tanto en Mac,Linux y con Everest en win,uso
> Ubuntu Ultimate 2.7 con kernel 2.6.32-24 y nada k no me funciona,Podria cmbiar
> el Id para k sea compatible?? ..bueno muchas gracias por tu atencion
Can you please share your Windows driver INF file ?
Luis
^ permalink raw reply
* Re: Atheros 0cf3:b003
From: Luis R. Rodriguez @ 2010-07-26 18:29 UTC (permalink / raw)
To: sergi; +Cc: linux-wireless, Stephen Chen
In-Reply-To: <AANLkTin7cn_TgEeepaWrE4sTuu5YxqPNDTDs-hxCs0vC@mail.gmail.com>
On Mon, Jul 26, 2010 at 11:29 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Sat, Jul 24, 2010 at 1:04 AM, sergi <sergitfe1974@gmail.com> wrote:
>> Luis R. Rodriguez <mcgrof@...> writes:
>>
>>>
>>> 2010/7/23 Maximi89 <maximi89@...>:
>>> > Hola Luis, conoces ese ID?, Atheros 0cf3:b003
>>> > Es efectivamente un AR9271?
>>>
>>> No, cual tarjeta es esa? Las que tenemos son estos:
>>>
>>
>>> { },
>>> };
>>>
>>> Stephen, have you heard of 0cf3:b003 as an ar9271 or HB94 card?
>>>
>>> Luis
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>>> the body of a message to majordomo@...
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>> Hola Luis yo fui quien le mando la consulta a maximiliano,,mi lapiz usb es de
>> la casa Ubiquiti modelo wifistation ext y ahi dicen k tiene el atheros 9271..y
>> el id k me sale es el mencionado,,tanto en Mac,Linux y con Everest en win,uso
>> Ubuntu Ultimate 2.7 con kernel 2.6.32-24 y nada k no me funciona,Podria cmbiar
>> el Id para k sea compatible?? ..bueno muchas gracias por tu atencion
>
> Can you please share your Windows driver INF file ?
Forgot to CC Stephen, please include him in your replies.
Luis
^ permalink raw reply
* Re: [PATCH 4/5] wireless: use newly introduced hex_to_bin()
From: John W. Linville @ 2010-07-26 18:27 UTC (permalink / raw)
To: Andy Shevchenko
Cc: David S. Miller, netdev, linux-kernel, Corey Thomas,
linux-wireless
In-Reply-To: <9d7821ff7791c30772667681c0eab829e6e93e59.1279890832.git.andy.shevchenko@gmail.com>
On Fri, Jul 23, 2010 at 04:18:09PM +0300, Andy Shevchenko wrote:
> Signed-off-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Cc: Corey Thomas <coreythomas@charter.net>
> Cc: "John W. Linville" <linville@tuxdriver.com>
> Cc: linux-wireless@vger.kernel.org
Acked-by: John W. Linville <linville@tuxdriver.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* RE: [PATCH v2 19/20] omap: zoom: keep the MMC3 wl1271 device powered off
From: Gabay, Benzy @ 2010-07-26 18:33 UTC (permalink / raw)
To: Ohad Ben-Cohen
Cc: linux-wireless@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux@arm.linux.org.uk, Chikkature Rajashekar, Madhusudhan,
Luciano Coelho, akpm@linux-foundation.org, San Mehat,
Roger Quadros, Tony Lindgren, Nicolas Pitre, Pandita, Vikram,
Kalle Valo
In-Reply-To: <AANLkTim3RWv2-qi9UMg1imwKTJuh3GstdjMTxz64uOHf@mail.gmail.com>
Ohad,
> -----Original Message-----
> From: Ohad Ben-Cohen [mailto:ohad@wizery.com]
> Sent: Thursday, July 22, 2010 6:18 PM
> To: Gabay, Benzy
> Cc: linux-wireless@vger.kernel.org; linux-mmc@vger.kernel.org; linux-
> omap@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> linux@arm.linux.org.uk; Chikkature Rajashekar, Madhusudhan; Luciano
> Coelho; akpm@linux-foundation.org; San Mehat; Roger Quadros; Tony
> Lindgren; Nicolas Pitre; Pandita, Vikram; Kalle Valo
> Subject: Re: [PATCH v2 19/20] omap: zoom: keep the MMC3 wl1271 device
> powered off
>
> Hi Gever,
>
> On Wed, Jul 21, 2010 at 9:55 PM, Gabay, Benzy <benzyg@ti.com> wrote:
> > From: Ohad Ben-Cohen [mailto:ohad@wizery.com]
> > Sent: Wednesday, July 21, 2010 12:34 PM
> > To: linux-wireless@vger.kernel.org; linux-mmc@vger.kernel.org; linux-
> omap@vger.kernel.org
> > Cc: linux-arm-kernel@lists.infradead.org; linux@arm.linux.org.uk;
> Chikkature Rajashekar, Madhusudhan; Luciano Coelho; akpm@linux-
> foundation.org; San Mehat; Roger Quadros; Tony Lindgren; Nicolas Pitre;
> Pandita, Vikram; Kalle Valo; Ohad Ben-Cohen
> > Subject: [PATCH v2 19/20] omap: zoom: keep the MMC3 wl1271 device
> powered off
> >
> > Keep the MMC3 wl1271 WLAN device powered off until its
> > SDIO function driver requests otherwise.
> >
> > Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> > ---
> > arch/arm/mach-omap2/board-zoom-peripherals.c | 1 +
> > arch/arm/mach-omap2/hsmmc.c | 3 +++
> > arch/arm/mach-omap2/hsmmc.h | 1 +
> > arch/arm/plat-omap/include/plat/mmc.h | 3 +++
> > drivers/mmc/host/omap_hsmmc.c | 3 +++
> > 5 files changed, 11 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
> b/arch/arm/mach-omap2/board-zoom-peripherals.c
> > index 3230801..3ab9125 100644
> > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c
> > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
> > @@ -217,6 +217,7 @@ static struct omap2_hsmmc_info mmc[] __initdata =
> {
> > .gpio_wp = -EINVAL,
> > .gpio_cd = -EINVAL,
> > .ocr_mask = MMC_VDD_165_195,
> > + .dont_power_card = true,
> > .priv_data = &omap_zoom_wlan_data,
> > },
> > {} /* Terminator */
> ...
> > --
> > 1.7.0.4
> >
> > [Benzy Gabay] small comment: Please make sure that all 127x related
> changes are not bounded only to MMC3.
> > On OMAP4 WLAN is used on MMC5.
>
>
> The only place MMC3 is bound is in the board files (see code snippet
> above), so that should be ok.
>
> I can probably split this patch to make this more obvious just by
> reading the diffstat if you prefer.
Yep. That will be great.
Benzy
>
>
> Thanks,
> Ohad.
>
>
> >
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox