From: Holger Schurig <holgerschurig@googlemail.com>
To: David Kilroy <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org, sameo@linux.intel.com, dcbw@redhat.com
Subject: Re: [RFC 0/2] cfg80211: Retrieve missing BSS info after connect
Date: Sat, 6 Feb 2010 18:27:48 +0100 [thread overview]
Message-ID: <201002061827.48913.holgerschurig@gmail.com> (raw)
In-Reply-To: <1265462416-7547-1-git-send-email-kilroyd@googlemail.com>
> It sounds like the libertas cfg80211 drivers have the same problem, so I'm
> posting them in case they're useful.
I'm not sure about that.
One thing that I'm sure of is that for the Libertas case I need to scan
*before* the connection takes place. The Libertas firmware doesn't roam by
itself, so I don't tell her an SSID like you'll tell the orinoco firmware.
Instead the libertas firmware needs a BSSID where it should connect to. If
you let do wpa_supplicant do the job (even for WEP), that's no problem,
because wpa_supplicant always scans and then connects to a specific BSSID,
which suits Libertas very well.
As for sending back then cfg80211_connect_result() to cfg80211, I'm using
the IEs from the firmware CMD_802_11_ASSOCIATE command, which seems to work
quite nicely.
The only thing where Libertas would need a scan during connect if someone
tries to connect to an AP without a previous scan using the "iw wlan0
connect" command. Not sure what Simon did here, but my previous v4 patch
simply failed.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2010-02-06 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 13:20 [RFC 0/2] cfg80211: Retrieve missing BSS info after connect David Kilroy
2010-02-06 13:20 ` [RFC 1/2] cfg80211: generic trigger scan and callback on completion David Kilroy
2010-02-06 13:35 ` Johannes Berg
2010-02-06 13:20 ` [RFC 2/2] cfg80211: scan for missing BSS on connect completion David Kilroy
2010-02-06 13:38 ` Johannes Berg
2010-02-06 13:51 ` [RFC 0/2] cfg80211: Retrieve missing BSS info after connect Johannes Berg
2010-02-06 18:26 ` Dave
2010-02-06 18:59 ` Johannes Berg
2010-02-06 17:27 ` Holger Schurig [this message]
2010-02-06 17:52 ` Dave
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=201002061827.48913.holgerschurig@gmail.com \
--to=holgerschurig@googlemail.com \
--cc=dcbw@redhat.com \
--cc=kilroyd@googlemail.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 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).