From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
Tsang-Shian Lin <thlin@realtek.com>,
Ping-Ke Shih <pkshih@realtek.com>,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
Birming Chiu <birming@realtek.com>, Shaofu <shaofu@realtek.com>,
Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH 2/3] rtlwifi: Add beacon check mechanism to check if AP settings changed.
Date: Tue, 19 Dec 2017 10:41:15 +0100 [thread overview]
Message-ID: <1513676475.26145.3.camel@sipsolutions.net> (raw)
In-Reply-To: <449108ee-32c1-0da9-8779-079beb659467@lwfinger.net> (sfid-20171214_170624_925221_BAD090A1)
On Thu, 2017-12-14 at 10:06 -0600, Larry Finger wrote:
> Does mac80211 have this facility? If so, how would we tap into it? If this
> capability does not exist in mac80211, how would one add it? I have never
> devoted much effort to looking at the internals of mac80211.
It really should, and this code looks awful - but can you tell me what
exactly this is doing?
If the AP changed settings, then we should handle this in
ieee80211_rx_mgmt_beacon() and simply reconfigure the driver
accordingly.
johannes
next prev parent reply other threads:[~2017-12-19 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 17:37 [PATCH 0/3] rtlwifi: rtl_pci: More updates to mini driver for RTL8822BE Larry Finger
2017-12-09 17:37 ` [PATCH 1/3] rtlwifi: rtl_pci: 8822BE puts broadcast and multicast packet to HIQ Larry Finger
2017-12-14 12:43 ` [1/3] " Kalle Valo
2017-12-09 17:37 ` [PATCH 2/3] rtlwifi: Add beacon check mechanism to check if AP settings changed Larry Finger
2017-12-14 12:35 ` Kalle Valo
2017-12-14 16:06 ` Larry Finger
2017-12-19 9:41 ` Johannes Berg [this message]
2017-12-09 17:37 ` [PATCH 3/3] rtlwifi: rtl_pci: Fix the bug when inactiveps is enabled Larry Finger
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=1513676475.26145.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=birming@realtek.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=shaofu@realtek.com \
--cc=steventing@realtek.com \
--cc=thlin@realtek.com \
--cc=yhchuang@realtek.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.