Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 20 7月, 2011 2 次提交
  3. 19 7月, 2011 1 次提交
  5. 16 7月, 2011 3 次提交
  7. 08 7月, 2011 1 次提交
  9. 07 7月, 2011 1 次提交
    • J
      cfg80211/nl80211: support GTK rekey offload · e5497d76
      由 Johannes Berg 提交于 
      In certain circumstances, like WoWLAN scenarios,
devices may implement (partial) GTK rekeying on
the device to avoid waking up the host for it.

In order to successfully go through GTK rekeying,
the KEK, KCK and the replay counter are required.

Add API to let the supplicant hand the parameters
to the driver which may store it for future GTK
rekey operations.

Note that, of course, if GTK rekeying is done by
the device, the EAP frame must not be passed up
to userspace, instead a rekey event needs to be
sent to let userspace update its replay counter.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      e5497d76
  11. 06 7月, 2011 4 次提交
  13. 28 6月, 2011 1 次提交
  15. 23 6月, 2011 3 次提交
    • G
      ath9k: add external_reset callback to ath9k_platfom_data for AR9330 · 7d95847c
      由 Gabor Juhos 提交于 
      The patch adds a callback to ath9k_platform_data. If the
callback is provided by the platform code, then it can be
used to hard reset the WMAC device.

The callback is required for doing a hard reset of the AR9330
chips to get them working again after a hang.
Signed-off-by: NGabor Juhos <juhosg@openwrt.org>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      7d95847c
    • G
      ath9k: add MAC revision detection for AR9330 · 3762561a
      由 Gabor Juhos 提交于 
      The AR9330 1.0 and 1.1 are using the same revision,
thus it is not possible to distinguish the two chips.
The platform setup code can distinguish the chips based
on the SoC revision.

Add a callback function to ath9k_platform_data in order
to allow getting the revision number from the platform code.
Signed-off-by: NGabor Juhos <juhosg@openwrt.org>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3762561a
    • J
      netlink: advertise incomplete dumps · 670dc283
      由 Johannes Berg 提交于 
      Consider the following situation:
 * a dump that would show 8 entries, four in the first
   round, and four in the second
 * between the first and second rounds, 6 entries are
   removed
 * now the second round will not show any entry, and
   even if there is a sequence/generation counter the
   application will not know

To solve this problem, add a new flag NLM_F_DUMP_INTR
to the netlink header that indicates the dump wasn't
consistent, this flag can also be set on the MSG_DONE
message that terminates the dump, and as such above
situation can be detected.

To achieve this, add a sequence counter to the netlink
callback struct. Of course, netlink code still needs
to use this new functionality. The correct way to do
that is to always set cb->seq when a dumpit callback
is invoked and call nl_dump_check_consistent() for
each new message. The core code will also call this
function for the final MSG_DONE message.

To make it usable with generic netlink, a new function
genlmsg_nlhdr() is needed to obtain the netlink header
from the genetlink user header.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Acked-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      670dc283
  17. 21 6月, 2011 1 次提交
  19. 11 6月, 2011 1 次提交
  21. 04 6月, 2011 3 次提交
  23. 02 6月, 2011 3 次提交
  25. 28 5月, 2011 3 次提交
  27. 27 5月, 2011 3 次提交
  29. 26 5月, 2011 1 次提交
  31. 23 5月, 2011 9 次提交