From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: scan_request->nr_ssids never 0 ?
Date: Tue, 29 Sep 2009 16:04:06 +0200 [thread overview]
Message-ID: <1254233047.30589.0.camel@johannes.local> (raw)
In-Reply-To: <200909291518.46655.hs4233@mail.mn-solutions.de>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
On Tue, 2009-09-29 at 15:18 +0200, Holger Schurig wrote:
> Even when I do an "iw xxx scan trigger", scan_request->nr_ssids
> is always 1 in my driver.
>
> Is this a bug or a feature?
# iw wlan0 scan trigger passive
> However, scan_request->ssids[0].ssid_len is 0.
>
> So to ask my firmware for an SSID scan, I need to do
>
> if (req->n_ssids && req->ssid[0].ssid_len)
>
> instead of simply
>
> if (req->n_ssids)
No. You need to ask it to probe for the wildcard SSID, which is 0 bytes
long.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-09-29 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 13:18 scan_request->nr_ssids never 0 ? Holger Schurig
2009-09-29 14:04 ` Johannes Berg [this message]
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=1254233047.30589.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=hs4233@mail.mn-solutions.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox