All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] libertas: cfg80211 support
Date: Thu, 11 Feb 2010 13:24:57 +0100	[thread overview]
Message-ID: <201002111324.57501.holgerschurig@gmail.com> (raw)
In-Reply-To: <20100211120133.GA3136@sortiz.org>

> What I changed is triggerring the scan work whenever the last
> one is done, i.e. triggering it from lbs_ret_scan().

Ah, that makes sense.

> My initial thought was that you could have 2 lbs_cfg_scan()
> running at the same time since you could potentially have a 2nd
> lbs_cfg_scan() call before scan_request is actually set.

Hmm, even when cfg80211 would allow this, I wouldn't allow this 
in the driver. All the hoops with the delayed-scan-work is 
because the firmware can't send a I'm-on-powersafe-notification 
to the current AP while being on other channels. So I have to 
make sure to return from time to time to my AP, so that I won't 
loose packets for me and won't be disconnected.

If now two scan_req and therefore two scan workers run, the time 
we're away from our "home channel" increases, which also 
increase the deauthentication problem.


Oh, and btw: we can later add an optimization that if we aren't 
connected at all, we do all scans in one-go, without delays. We 
still need to send several scan-commands to the firmware, to 
reduce the possible that a huuuuuge scan response overflows some 
firmware buffer limit.


Thanks for your answers.

Best regards,
Holger

-- 
http://www.holgerschurig.de

  reply	other threads:[~2010-02-11 12:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  0:09 [PATCH] libertas: cfg80211 support Samuel Ortiz
2010-02-02 20:36 ` John W. Linville
2010-02-03  9:31   ` Holger Schurig
2010-02-03 12:04     ` Samuel Ortiz
2010-02-03 15:32       ` Holger Schurig
2010-02-03 20:30         ` Dan Williams
2010-02-04  7:28           ` Holger Schurig
2010-02-04 21:49             ` Dan Williams
2010-02-04  9:52 ` Holger Schurig
2010-02-11 12:01   ` Samuel Ortiz
2010-02-11 12:24     ` Holger Schurig [this message]
2010-02-04 10:11 ` Holger Schurig
2010-02-11 12:03   ` Samuel Ortiz
2010-02-04 13:44 ` [PATCH] libertas+cfg80211: better disconnect support Holger Schurig
2010-02-15 10:46 ` [PATCH] libertas: cfg80211 support Holger Schurig
     [not found]   ` <cdd918981002240005o1fa50956yfb2a692716c06a55@mail.gmail.com>
2010-02-24 23:35     ` Dan Williams
2010-02-25  8:42       ` David MOUSSAUD
2010-02-25  8:48         ` Johannes Berg
2010-02-25 18:05           ` Andrey Yurovsky
2010-03-07 17:32             ` Kalle Valo
2010-03-07 17:52               ` Gábor Stefanik
2010-02-24  8:22 ` David MOUSSAUD

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=201002111324.57501.holgerschurig@gmail.com \
    --to=holgerschurig@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.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 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.