linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Kalle Valo <kalle.valo@iki.fi>, Matthew Garrett <mjg@redhat.com>,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: wireless powersaving (in NM?)
Date: Wed, 25 Mar 2009 11:31:12 -0400	[thread overview]
Message-ID: <1237995072.18896.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1237979070.4320.156.camel@johannes.local>

On Wed, 2009-03-25 at 12:04 +0100, Johannes Berg wrote:
> On Tue, 2009-03-24 at 11:59 -0400, Dan Williams wrote:
> 
> > or maybe gnome-power-manager (and whatever the kde equivalent is) should
> > be driving this based on all the other policy decisions it makes?  it's
> > the thing that handles whether you're on battery or on AC, what your
> > drive spin-down time is, it knows when your laptop lid is closed, what
> > your display brightness is at, etc.
> > 
> > it might use some information from NM as input, but the overall power
> > manager is probably where the actual policy decisions should be made.
> 
> Makes sense too. I guess that Marcel makes a compelling case for it
> always being enabled, and Kalle says we need to have an override --
> which semantically needs to be in NM/connman since that's where the user
> will look if the connection is flaky (because the AP is broken)

Yeah, sounds OK.  Just to be clear, problems with this code will appear
on a *per-AP* basis, not a per-card basis, right?  ie there are some
stupid APs that won't work with it, but it won't be the case that a
chipset will be broken for all APs, right?

Dan



  reply	other threads:[~2009-03-25 15:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 10:39 wireless powersaving (in NM?) Johannes Berg
2009-03-24 10:32 ` Marcel Holtmann
2009-03-25 10:45   ` Johannes Berg
2009-03-24 13:47 ` John W. Linville
2009-03-24 13:53 ` Johannes Berg
2009-03-24 14:47   ` Guy, Wey-Yi W
2009-03-24 15:03     ` Kalle Valo
2009-03-24 14:17 ` Kalle Valo
2009-03-25 10:57   ` Johannes Berg
2009-03-25 19:53     ` Kalle Valo
2009-03-25 20:06       ` Johannes Berg
2009-03-25 20:09         ` Johannes Berg
2009-03-25 20:22         ` Kalle Valo
2009-03-24 15:59 ` Dan Williams
2009-03-25 11:04   ` Johannes Berg
2009-03-25 15:31     ` Dan Williams [this message]
2009-03-25 15:48       ` Johannes Berg
2009-03-26  8:00         ` Luis R. Rodriguez
2009-03-26  8:11           ` Johannes Berg
2009-03-26  8:39             ` Luis R. Rodriguez
2009-03-26  8:54               ` Johannes Berg
2009-03-26  9:01                 ` Luis R. Rodriguez
2009-03-26 14:29                   ` Georgy Berdyshev
2009-03-26  8:19           ` Kalle Valo
2009-03-26  8:40             ` Luis R. Rodriguez
2009-03-31 16:28 ` Johannes Berg
2009-04-01 11:04 ` more thoughts on power saving (was: wireless powersaving (in NM?)) Johannes Berg
2009-04-01 11:12   ` Kalle Valo
2009-04-01 14:29     ` Guy, Wey-Yi W

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=1237995072.18896.9.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mjg@redhat.com \
    --cc=wey-yi.w.guy@intel.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).