From: Dave <kilroyd@googlemail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: question about cfg80211_inform_bss()
Date: Tue, 06 Oct 2009 18:42:39 +0100 [thread overview]
Message-ID: <4ACB818F.7000508@gmail.com> (raw)
In-Reply-To: <200910061418.05039.hs4233@mail.mn-solutions.de>
Holger Schurig wrote:
> However, cfg80211_inform_bss() want's a channel. And it wants the
> IEs as well. A presume it scans those IEs, too. So do we need to
> parse the IEs twice?
That is what orinoco does.
It's slightly worse for non-WPA firmware on orinoco. They supply ssid
and supported rates in a structure, and don't give access to the
original IEs - so the driver has to reconstruct the approporiate IE as
best it can, so cfg80211 can export them (all in orinoco/scan.c).
Dave.
prev parent reply other threads:[~2009-10-06 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 12:18 question about cfg80211_inform_bss() Holger Schurig
2009-10-06 17:42 ` Dave [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=4ACB818F.7000508@gmail.com \
--to=kilroyd@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).