From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Jouni Malinen <j@w1.fi>
Subject: generic IE and AP mode
Date: Thu, 20 Sep 2007 03:58:46 +0200 [thread overview]
Message-ID: <1190253526.18521.12.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Hey,
Currently we have some sort of support for hardware that generates
beacons independently. However, we have no such hardware. Hostapd,
however, requires that SIOCSIWGENIE doesn't fail. I suppose it can be
taught to ignore it.
However, the question is whether we want to support such hardware
designs in mac80211. I tend to not want to with the ever increasing
complexity and number of fields in the beacon. Where should the "generic
element" be inserted into the beacon? Last? After the TIM? Then how does
the hardware know what to include in the supported rates element etc?
Does anyone object to just getting rid of it?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
reply other threads:[~2007-09-20 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1190253526.18521.12.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--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