Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Paul Stewart <pstew@google.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Amod Bodas <amod@atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Push idle state to driver before stop
Date: Wed, 5 Jan 2011 10:26:17 -0800	[thread overview]
Message-ID: <20110105182617.GB10391@tux> (raw)
In-Reply-To: <AANLkTikDP_uF_jGh5bNyMv17VoZB=9u-SrdWRUQ15gRb@mail.gmail.com>

On Tue, Jan 04, 2011 at 02:29:53PM -0800, Paul Stewart wrote:
> On Tue, Jan 4, 2011 at 10:19 AM, Paul Stewart <pstew@google.com> wrote:
> > On Thu, Dec 16, 2010 at 9:44 AM, Luis R. Rodriguez
> > <lrodriguez@atheros.com> wrote:
> >> Try this:
> >
> > Happy new year.  I've tried this patch, and the system continues to
> > suspend and resume successfully (i.e, the fix from the earlier patches
> > continues to alleviate the original problem), however the system
> > continues to be "deaf" to beacons at resume time if the system
> > suspends and resumes while associated.  You don't need a ChromeOS
> > system to reproduce this issue.  Just associate to the network and
> > suspend/resume.  On resume the system believes it should be
> > associated, but then the beacon loss timer kicks in and we
> > disassociate, since we are never successful in receiving a response.
> 
> Whoops.  I didn't apply that change correctly.  Actually, I think this
> change works.  I think I may have spotted a couple of unrelated
> anomalies I'll trace down and address separately.

Great, I think this patch got sucked up already, I'll check.

  Luis

  reply	other threads:[~2011-01-05 18:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 18:54 [PATCH] mac80211: Push idle state to driver before stop Paul Stewart
2010-12-16  6:59 ` Johannes Berg
2010-12-16 11:17   ` Paul Stewart
2010-12-16 11:30     ` Johannes Berg
2010-12-16 11:51       ` Paul Stewart
2010-12-16 12:04         ` Johannes Berg
2010-12-16 12:27           ` Paul Stewart
2010-12-16 12:35             ` Johannes Berg
2010-12-16 12:46               ` Paul Stewart
2010-12-16 12:53                 ` Johannes Berg
2010-12-16 16:02                   ` Paul Stewart
2010-12-16 17:44                     ` Luis R. Rodriguez
2010-12-16 17:49                       ` Luis R. Rodriguez
2010-12-16 19:08                       ` Paul Stewart
2010-12-16 19:12                         ` Luis R. Rodriguez
2011-01-04 18:19                       ` Paul Stewart
2011-01-04 22:29                         ` Paul Stewart
2011-01-05 18:26                           ` Luis R. Rodriguez [this message]
2011-01-05 22:57                             ` 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=20110105182617.GB10391@tux \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=amod@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pstew@google.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