All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jake Edge <jake@lwn.net>
Subject: Re: [RFT/RFC 0/4] iwlegacy: workaround for firmware frame tx rejection
Date: Sat, 25 May 2013 10:53:00 +0200	[thread overview]
Message-ID: <20130525085259.GB1599@redhat.com> (raw)
In-Reply-To: <1369427208.8290.35.camel@jlt4.sipsolutions.net>

On Fri, May 24, 2013 at 10:26:48PM +0200, Johannes Berg wrote:
> On Thu, 2013-05-23 at 14:20 +0200, Stanislaw Gruszka wrote:
> > Jake, please test this set and check if it not cause association
> > problems you reported earlier this month.
> > 
> > Please apply it together with this mac80211 patch:
> > http://marc.info/?l=linux-wireless&m=136879090123023&w=2 
> > which I already posted and is queued to upstream. Not having
> > it may cause troubles and influence negatively this set test.
> > 
> > Johannes, is need to check beacon bssid or even if rx frame
> > is a beacon to unblock queues? I think if we receive any frame
> > (not necessary beacon or our bssid beacon) on passive channel,
> > that mean we can use that channel. But that depend how firmware
> > is implemented, if firmware require our bssid beacon to unblock
> > channel, driver of course need that too.
> 
> I _think_ any frame with good CRC will do, but I'm not entirely sure for
> 3945/4965.

I prefer to unblock queues on any frame, as this allow to start
operating quickly.  Let's see if this will also work on Jake environment,
I'll add patch 5/4 which implement that.

Stanislaw

  reply	other threads:[~2013-05-25  8:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 12:20 [RFT/RFC 0/4] iwlegacy: workaround for firmware frame tx rejection Stanislaw Gruszka
2013-05-23 12:20 ` [RFT/RFC 1/4] iwlegacy: small refactoring of il_{stop,wake}_queue Stanislaw Gruszka
2013-05-23 12:20 ` [RFT/RFC 2/4] iwlegacy: add il_{stop,wake}_queues_by_reason functions Stanislaw Gruszka
2013-05-23 12:20 ` [RFT/RFC 3/4] iwlegacy: workaround for firmware frame tx rejection Stanislaw Gruszka
2013-05-23 12:21 ` [RFT/RFC 4/4] Revert "iwl4965: workaround connection regression on passive channel" Stanislaw Gruszka
2013-05-25  8:55   ` [RFT/RFC 5/4] iwlegacy: unblock queues on passive channel if any frame receive Stanislaw Gruszka
2013-05-24 20:26 ` [RFT/RFC 0/4] iwlegacy: workaround for firmware frame tx rejection Johannes Berg
2013-05-25  8:53   ` Stanislaw Gruszka [this message]
2013-05-24 23:18 ` Jake Edge
2013-05-25  6:49   ` Stanislaw Gruszka
2013-06-10 20:38 ` Jake Edge
2013-06-11  3:41   ` Jake Edge
2013-06-11 16:09     ` Stanislaw Gruszka
2013-06-11 19:17       ` Jake Edge
2013-06-12 14:39         ` Stanislaw Gruszka

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=20130525085259.GB1599@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=jake@lwn.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.