From: Fabio Rossi <rossi.f@inwind.it>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Davide Pesavento <davidepesa@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] mac80211 powersave work
Date: Mon, 20 Apr 2009 23:55:46 +0200 [thread overview]
Message-ID: <200904202355.46803.rossi.f@inwind.it> (raw)
In-Reply-To: <1240259450.4632.20.camel@johannes.local>
On Monday 20 April 2009, Johannes Berg wrote:
> But if that's just a hardware/driver bug shouldn't the driver disable PS
> for that combination? It seems wrong to disable PS in the stack by
> default just because one driver has a problem with it, when that driver
> could just unset the PS support bit.
I think that a printk notice message could be useful to state that the
powersave management is active (of course with DEBUG on, at least during the
first larger-user-base test period).
Fabio
next prev parent reply other threads:[~2009-04-20 21:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 11:17 [PATCH 0/4] mac80211 powersave work Johannes Berg
2009-04-16 11:17 ` [PATCH 1/4] mac80211: improve powersave implementation Johannes Berg
2009-04-16 11:17 ` [PATCH 2/4] mac80211: disable powersave if pm_qos asks for low latency Johannes Berg
2009-04-16 11:17 ` [PATCH 3/4] mac80211: implement beacon filtering in software Johannes Berg
2009-04-16 11:17 ` [PATCH 4/4] mac80211: enable PS by default Johannes Berg
2009-04-16 11:27 ` [PATCH 4/4 v2] " Johannes Berg
2009-04-20 19:44 ` [PATCH 0/4] mac80211 powersave work John W. Linville
2009-04-20 19:53 ` Johannes Berg
2009-04-20 20:26 ` Davide Pesavento
2009-04-20 20:30 ` Johannes Berg
2009-04-20 21:19 ` Davide Pesavento
2009-04-20 21:28 ` Johannes Berg
2009-04-20 21:55 ` Fabio Rossi [this message]
2009-04-20 21:03 ` John W. Linville
2009-04-21 5:24 ` Kalle Valo
2009-04-21 12:51 ` John W. Linville
2009-04-21 13:09 ` Kalle Valo
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=200904202355.46803.rossi.f@inwind.it \
--to=rossi.f@inwind.it \
--cc=davidepesa@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).