From: Dave <kilroyd@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, holgerschurig@gmail.com,
sameo@linux.intel.com, dcbw@redhat.com
Subject: Re: [RFC 0/2] cfg80211: Retrieve missing BSS info after connect
Date: Sat, 06 Feb 2010 18:26:22 +0000 [thread overview]
Message-ID: <4B6DB44E.7030201@gmail.com> (raw)
In-Reply-To: <1265464303.4041.24.camel@johannes.local>
Johannes Berg wrote:
> On Sat, 2010-02-06 at 13:20 +0000, David Kilroy wrote:
>> This patchset attempts to address the issue where a driver that uses
>> the cfg80211 connect operation connects to an AP before the scan result
>> for the AP is available. This triggers a WARN_ON in sme.c, and the
>> connection fails.
>
> With technical comments out of the way (see other emails) I guess I want
> to know whether this really makes sense.
>
> Yes, we definitely need the right BSS struct when the driver signals
> that it connected, but we also need the same information when it roamed
> for example. Does it really make sense to scan after the fact, instead
> of asking the driver to provide the information? This is a genuine
> question -- I can see value in this if more than one driver needs it,
> but if the devices can just provide BSS information right before the
> connected call that would be a lot simpler here.
Thanks for the feedback. Like I said, the main point of posting was to
see if this logic helped libertas in any way. Sounds like it doesn't, so
I won't push this for now. When I get round to looking at orinoco again
I'll see if I can handle this within the driver. If not I'll address the
issues you've raised.
I don't think orinoco can provide the BSS info without explicitly doing
the scan (whether internally or via cfg80211). Even if I could get it to
work for the firmware version I have, there's no guarantee that it'll
work for the other supported firmware types (that I don't have).
Dave.
next prev parent reply other threads:[~2010-02-06 18:26 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 [this message]
2010-02-06 18:59 ` Johannes Berg
2010-02-06 17:27 ` Holger Schurig
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=4B6DB44E.7030201@gmail.com \
--to=kilroyd@googlemail.com \
--cc=dcbw@redhat.com \
--cc=holgerschurig@gmail.com \
--cc=johannes@sipsolutions.net \
--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.