From: Kalle Valo <kvalo@adurom.com>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA
Date: Thu, 24 May 2012 09:36:46 +0300 [thread overview]
Message-ID: <87aa0y6q69.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CA+XVXffb3tZ2_kWwx0wBWUac-y0BPTT_KBJ5yhxNjPVp4U7HGw@mail.gmail.com> (Arik Nemtsov's message of "Thu, 24 May 2012 08:32:14 +0300")
Arik Nemtsov <arik@wizery.com> writes:
> On Thu, May 24, 2012 at 8:12 AM, Kalle Valo <kvalo@adurom.com> wrote:
>> But this was a workaround for an IOP problem with certain APs, right?
>> How is firmware going to be smart in that case?
>>
>> It would help to see what you are exactly planning to do on wl12xx with
>> this interface. Currently I'm just guessing what your plans really are.
>
> The plan is to enable only VO as U-APSD (as I wrote in a previous
> email).
You mean you will hardcode it in wl12xx and with all APs only VO has
U-APSD enabled?
> We've had problems with some APs (can't remember the models) that
> assume non-VO ACs always use legacy PS. This would lead to problems -
> our driver would never wake up. In that sense the problem is general.
Yeah, that looks like a general problem but of course it's difficult to
make any conclusions with this little data.
--
Kalle Valo
prev parent reply other threads:[~2012-05-24 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 8:13 [PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA Arik Nemtsov
2012-05-23 10:44 ` Kalle Valo
2012-05-23 10:49 ` Arik Nemtsov
2012-05-23 10:59 ` Kalle Valo
2012-05-23 11:13 ` Arik Nemtsov
2012-05-23 14:22 ` Kalle Valo
2012-05-23 14:35 ` Arik Nemtsov
2012-05-24 5:12 ` Kalle Valo
2012-05-24 5:32 ` Arik Nemtsov
2012-05-24 6:05 ` Janusz Dziedzic
2012-05-24 6:39 ` Kalle Valo
2012-05-25 5:37 ` Arik Nemtsov
2012-05-25 9:59 ` Janusz Dziedzic
2012-05-24 6:36 ` Kalle Valo [this message]
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=87aa0y6q69.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=arik@wizery.com \
--cc=johannes@sipsolutions.net \
--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