From: Christian Lamparter <chunkeey@web.de>
To: "Bob Copeland" <me@bobcopeland.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 6/6] ar9170: stop data queues on channel switch
Date: Tue, 12 May 2009 18:56:02 +0200 [thread overview]
Message-ID: <200905121856.02714.chunkeey@web.de> (raw)
In-Reply-To: <20090512154116.M40327@bobcopeland.com>
On Tuesday 12 May 2009 17:56:10 Bob Copeland wrote:
> On Tue, 12 May 2009 17:30:27 +0200, Johannes Berg wrote
> > On Tue, 2009-05-12 at 11:29 -0400, Bob Copeland wrote:
> > > Will pre-scan be called once per scan or once for every channel switch?
> > > If the former, I think it's not the right place to flush.
> >
> > The former.
>
> Hmm, nevermind, it should work. I was thinking of queued tx status
> work not being on the right channel, but I guess we don't do that for probe
> requests.
Ermm? wait... what do we do when the userspace does channel switch & scans?
I think, some aircrack tools actually do this. Will they also call pre_scan?
> And for ar9170 RX is processed synchronously as far as I can tell.
most of the time yes... unless we have to _reconstruct_ a stream, because
the hw/fw clipped a few byte from a frame.
Regards,
Chr
next prev parent reply other threads:[~2009-05-12 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 23:09 [PATCH 6/6] ar9170: stop data queues on channel switch Christian Lamparter
2009-05-12 6:39 ` Johannes Berg
2009-05-12 15:15 ` Christian Lamparter
2009-05-12 16:45 ` Johannes Berg
2009-05-12 15:29 ` Bob Copeland
2009-05-12 15:30 ` Johannes Berg
2009-05-12 15:56 ` Bob Copeland
2009-05-12 16:56 ` Christian Lamparter [this message]
2009-05-12 17:51 ` Johannes Berg
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=200905121856.02714.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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 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.