From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Subject: Re: ieee80211_rx_mgmt: pushing fake 'management' frames into userspace
Date: Wed, 27 Jun 2007 17:30:59 +0200 [thread overview]
Message-ID: <200706271730.59591.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1182952910.4769.20.camel@johannes.berg>
> Also, I thought you were doing a fullmac chipset? Then you
> shouldn't be worrying about mac80211 *at all*
Yes, unfortunately.
Currently, Linux has only fullmac and softmac. However, I'm
working with a half-soft-half-full-mac hardware (libertas). What
I mean is that the generation of the low-level packets etc are
all done by the firmware in the card (fullmac). However,
issueing scans (for IBSS or Managed mode), selecting a proper AP
from the scan result, associating etc are all commands that the
PC has to send to the firmware.
Some of this is not yet correctly working, e.g. when I kick out
the WLAN card from the AP, then libertas just notifies this, but
stays up ... it doesn't re-scan and re-associates. There are
other scenarios where the current libertas code doesn't
automatically re-scan/re-associate as well.
All of this is included in net/mac80211/ieee80211_sta.c, but
tightly coupled to mac80211 so that it is unusable for
non-mac80211 cards. Sigh.
next prev parent reply other threads:[~2007-06-27 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 13:25 ieee80211_rx_mgmt: pushing fake 'management' frames into userspace Mandy.Peng
2007-06-27 14:01 ` Johannes Berg
2007-06-27 14:01 ` Johannes Berg
2007-06-27 15:30 ` Holger Schurig [this message]
2007-06-27 16:59 ` Dan Williams
2007-06-28 9:55 ` Johannes Berg
2007-06-28 8:40 ` ieee80211_rx_mgmt: pushing fake 'management' frames intouserspace Mandy.Peng
2007-06-28 9:38 ` Johannes Berg
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=200706271730.59591.hs4233@mail.mn-solutions.de \
--to=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