Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 26 11月, 2012 2 次提交
    • J
      cfg80211: remove remain-on-channel channel type · 42d97a59
      由 Johannes Berg 提交于 
      As mwifiex (and mac80211 in the software case) are the
only drivers actually implementing remain-on-channel
with channel type, userspace can't be relying on it.
This is the case, as it's used only for P2P operations
right now.

Rather than adding a flag to tell userspace whether or
not it can actually rely on it, simplify all the code
by removing the ability to use different channel types.
Leave only the validation of the attribute, so that if
we extend it again later (with the needed capability
flag), it can't break userspace sending invalid data.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      42d97a59
    • A
      cfg80211: change function signature of cfg80211_get_p2p_attr() · c216e641
      由 Arend van Spriel 提交于 
      The function cfg80211_get_p2p_attr() can fail and returns
a negative error code. However, the return type is unsigned
int. The largest positive number is determined by desired_len
variable in the function, which is u16. So changing the return
type to int to allow easy error checking. Also change the type
for the attribute to enum for improved type checking.
Signed-off-by: NArend van Spriel <arend@broadcom.com>
[fix indentation, don't use u8 attr variable]
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      c216e641
  3. 19 11月, 2012 1 次提交
    • J
      cfg80211: Add TDLS event to allow drivers to request operations · 3475b094
      由 Jouni Malinen 提交于 
      The NL80211_CMD_TDLS_OPER command was previously used only for userspace
request for the kernel code to perform TDLS operations. However, there
are also cases where the driver may need to request operations from
userspace, e.g., when using security on the AP path. Add a new cfg80211
function for generating a TDLS operation event for drivers to request a
new link to be set up (NL80211_TDLS_SETUP) or an existing link to be
torn down (NL80211_TDLS_TEARDOWN). Drivers can optionally use these
events, e.g., based on noticing data traffic being sent to a peer
station that is seen with good signal strength.
Signed-off-by: NJouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      3475b094
  5. 06 11月, 2012 1 次提交
    • J
      wireless: add utility function to get P2P attribute · 0ee45355
      由 Johannes Berg 提交于 
      Parsing the P2P attributes can be tricky as their
contents can be split across multiple (vendor) IEs.
Thus, it's not possible to parse them like IEs (by
returning a pointer to the data.) Instead, provide
a function that copies the attribute data into a
caller-provided buffer and returns the size needed
(useful in case the buffer was too small.)
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      0ee45355
  7. 05 11月, 2012 2 次提交
  9. 30 10月, 2012 1 次提交
    • J
      cfg80211: allow per interface TX power setting · c8442118
      由 Johannes Berg 提交于 
      The TX power setting is currently per wiphy (hardware
device) but with multi-channel capabilities that doesn't
make much sense any more.

Allow drivers (and mac80211) to advertise support for
per-interface TX power configuration. When the TX power
is configured for the wiphy, the wdev will be NULL and
the driver can still handle that, but when a wdev is
given the TX power can be set only for that wdev now.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      c8442118
  11. 27 10月, 2012 1 次提交
    • J
      mac80211: verify that skb data is present · 9b395bc3
      由 Johannes Berg 提交于 
      A number of places in the mesh code don't check that
the frame data is present and in the skb header when
trying to access. Add those checks and the necessary
pskb_may_pull() calls. This prevents accessing data
that doesn't actually exist.

To do this, export ieee80211_get_mesh_hdrlen() to be
able to use it in mac80211.

Cc: stable@vger.kernel.org
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      9b395bc3
  13. 18 10月, 2012 2 次提交
  15. 17 10月, 2012 2 次提交
  17. 15 10月, 2012 1 次提交
  19. 19 9月, 2012 3 次提交
  21. 11 9月, 2012 1 次提交
  23. 05 9月, 2012 1 次提交
  25. 20 8月, 2012 1 次提交
    • J
      cfg80211: add P2P Device abstraction · 98104fde
      由 Johannes Berg 提交于 
      In order to support using a different MAC address
for the P2P Device address we must first have a
P2P Device abstraction that can be assigned a MAC
address.

This abstraction will also be useful to support
offloading P2P operations to the device, e.g.
periodic listen for discoverability.

Currently, the driver is responsible for assigning
a MAC address to the P2P Device, but this could be
changed by allowing a MAC address to be given to
the NEW_INTERFACE command.

As it has no associated netdev, a P2P Device can
only be identified by its wdev identifier but the
previous patches allowed using the wdev identifier
in various APIs, e.g. remain-on-channel.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      98104fde
  27. 02 8月, 2012 1 次提交
  29. 17 7月, 2012 1 次提交
  31. 13 7月, 2012 2 次提交
    • J
      cfg80211: reduce monitor interface tracking · 4290cb4b
      由 Johannes Berg 提交于 
      Revert commit b78e8cea
("cfg80211: track monitor channel") and remove the
set_monitor_enabled() callback.

Due to the tracking happening in NETDEV_PRE_UP, it had
introduced bugs because the monitor interface callback
would be called before the device was started. It looks
like there's no way to fix this, and using NETDEV_PRE_UP
is broken anyway (since there's no NETDEV_UP_FAIL), so
remove all that code, track interfaces in NETDEV_UP and
also stop tracking the monitor channel in cfg80211.

This mostly reverts to before the tracking, except that
we keep the interface count tracking so that setting the
monitor channel can be rejected properly.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      4290cb4b
    • J
      cfg80211/mac80211: re-add get_channel operation · 5b7ccaf3
      由 Johannes Berg 提交于 
      This essentially reverts commit 2e165b81 but
introduces the get_channel operation with a new
wireless_dev argument so that you can retrieve
the channel per interface. This is necessary as
even though we can track all interface channels
(except monitor) we can't track the channel type
used.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      5b7ccaf3
  33. 12 7月, 2012 2 次提交
  35. 09 7月, 2012 2 次提交
    • J
      cfg80211: use wdev in mgmt-tx/ROC APIs · 71bbc994
      由 Johannes Berg 提交于 
      The management frame and remain-on-channel APIs will be
needed in the P2P device abstraction, so move them over
to the new wdev-based APIs. Userspace can still use both
the interface index and wdev identifier for them so it's
backward compatible, but for the P2P Device wdev it will
be able to use the wdev identifier only.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      71bbc994
    • J
      nl80211: prepare for non-netdev wireless devs · 89a54e48
      由 Johannes Berg 提交于 
      In order to support a P2P device abstraction and
Bluetooth high-speed AMPs, we need to have a way
to identify virtual interfaces that don't have a
netdev associated.

Do this by adding a NL80211_ATTR_WDEV attribute
to identify a wdev which may or may not also be
a netdev.

To simplify things, use a 64-bit value with the
high 32 bits being the wiphy index for this new
wdev identifier in the nl80211 API.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      89a54e48
  37. 05 7月, 2012 2 次提交
  39. 02 7月, 2012 1 次提交
  41. 29 6月, 2012 4 次提交
  43. 28 6月, 2012 1 次提交
  45. 27 6月, 2012 1 次提交
  47. 26 6月, 2012 1 次提交
  49. 18 6月, 2012 1 次提交
  51. 14 6月, 2012 1 次提交
  53. 13 6月, 2012 1 次提交