From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kalle.valo@iki.fi>
Subject: Re: p54 problem with PS
Date: Thu, 16 Apr 2009 22:18:24 +0200 [thread overview]
Message-ID: <1239913104.26575.25.camel@johannes.local> (raw)
In-Reply-To: <200904162157.20576.chunkeey@web.de>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
> Well, I guess I figured out what's wrong: the hw spec.
> So this patch might work on PCI & USB, but could break SPI devices.
Heh.
> Johannes, can you please test the attached patch?
>
> BTW: there might be two problems:
> 1. if the timeout is too low the device might be fast enough to go into ps:
> - either before sending a probe request
> (firmware reports tx_status TX_PSM, so the frame wasn't sent at all)
> - or the AP got the request and responded...
> But the frame was lost, because probe responds are not buffered...
?
> 2. there was something wrong in ieee80211_rx_mgmt_beacon
> Sometimes the TIM was parsed, but thanks to
> local->hw.conf.dynamic_ps_timeout == 0
> mac80211 didn't issue a wakeup => so no data => disconnect
>
> But this bug maybe comes from the old RFCs from yesterday,
> as I didn't tried the final version yet...
I didn't change that -- Kalle did that, see the comment there. I guess
we need to change that then.
> Oh and one question:
> Some time ago, I found some useful function that converted beacon_int TUs <-> msec,
> do we still have them somewhere around and I'm just (temp) blind ?
I just added TU -> msec in one of my patches to include/linux/ieee8021.h
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-16 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:24 p54 problem with PS Johannes Berg
2009-04-16 19:57 ` Christian Lamparter
2009-04-16 20:18 ` Johannes Berg [this message]
2009-04-17 11:56 ` Christian Lamparter
2009-04-17 12:08 ` Johannes Berg
2009-04-17 12:12 ` Johannes Berg
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=1239913104.26575.25.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=chunkeey@web.de \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@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