From: Kalle Valo <kalle.valo@iki.fi>
To: Holger Schurig <holgerschurig@googlemail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, linux-wireless@vger.kernel.org
Subject: Re: ar9170 in AP mode
Date: Mon, 09 Nov 2009 10:37:36 +0200 [thread overview]
Message-ID: <87ocncdrfz.fsf@purkki.valot.fi> (raw)
In-Reply-To: <m3639k9kq4.wl%holgerschurig@gmail.com> (Holger Schurig's message of "Mon\, 09 Nov 2009 09\:16\:19 +0100")
Holger Schurig <holgerschurig@googlemail.com> writes:
>> How common is the combination of powersaving and mcast in practice?
>> Given that quite a few useful scenarios are blocked right now (unless
>> you know what to patch), I would at least vote for a config option or a
>> module parameter. That gives a chance to warn the user about this
>> limitation without locking out people that are no hackers.
>
> In my case (hand-help devices) it's very common. Without power-save,
> the battery would be drained so fast it wouldn't be usable.
Yes, just to give a concrete example of n810 wlan idle case
(associated, but no data transfered):
ps off 7 hours
ps on 7 days
Huge difference.
> And with power-save and an AP that can't handle this, you'd get
> weird errors.
Exactly. These kinds of errors are very difficult for the users to
understand.
> So, I personally prefer to have "Do an AP right" or "Don't do it at
> all". But please no general enablement.
>
> But, for example, having some CONFIG_AR9K_AP_MODE depending on
> CONFIG_EXPERIMENTAL and a bit fat warning would do for me. Hopefully
> this would scara away distros, so that they don't turn this on for
> there standard kernel :-)
I think EXPERIMENTAL is not enough, I would prefer that the user needs
to patch the driver to enable it. Or if that's not good enough, then
maybe depend on BROKEN.
--
Kalle Valo
next prev parent reply other threads:[~2009-11-09 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 13:29 ar9170 in AP mode Jan Kiszka
2009-11-08 13:38 ` Kalle Valo
2009-11-08 13:47 ` Jan Kiszka
2009-11-08 14:01 ` Johannes Berg
2009-11-08 14:40 ` Jan Kiszka
2009-11-08 14:56 ` Johannes Berg
2009-11-09 8:16 ` Holger Schurig
2009-11-09 8:37 ` Kalle Valo [this message]
2009-11-09 14:14 ` John W. Linville
2009-11-09 21:09 ` Jan Kiszka
2009-11-10 10:39 ` Johannes Berg
2009-11-09 18:52 ` Jeffrey Baker
2009-11-09 19:49 ` Luis R. Rodriguez
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=87ocncdrfz.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=holgerschurig@googlemail.com \
--cc=jan.kiszka@web.de \
--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;
as well as URLs for NNTP newsgroup(s).