1. 28 Jan, 2008 1 commit
  2. 10 Oct, 2007 4 commits
    • Ivo van Doorn's avatar
      [PATCH] rt2x00: Fix rfkill handling · 81873e9c
      Ivo van Doorn authored
      As reported by Modestas Vainius, enabling rkfill in 1 driver and
      disabling it in a second could cause a NULL pointer exception when
      the rfkill-disabled driver still sets the CONFIG_SUPPORT_HW_BUTTON flag.
      Furthermore, rfkill expects the timeout as a value in milliseconds
      instead of jiffies. Also increase the timeout to a second,
      since this 250ms would be overkill.
      Also the flag DEVICE_ENABLED_RADIO_HW is causing problems
      for devices which do not support the hardware button
      while rfkill is enabled in the driver.
      To remidy this we should inverse the flag and its meaning,
      rename the flag to DEVICE_DISABLED_RADIO_HW this means that
      by default the radio is enabled by the hardware button (if present)
      and can only be disabled explicitely.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Ivo van Doorn's avatar
      [PATCH] rt2x00: Reorganize rt2x00dev->flags · 066cb637
      Ivo van Doorn authored
      The rt2x00dev->flags has become a chaos over time,
      this will reorganize the flags by renaming, deleting, adding
      and properly implement the flags.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Johannes Berg's avatar
      [PATCH] mac80211: revamp interface and filter configuration · 4150c572
      Johannes Berg authored
      Drivers are currently supposed to keep track of monitor
      interfaces if they allow so-called "hard" monitor, and
      they are also supposed to keep track of multicast etc.
      This patch changes that, replaces the set_multicast_list()
      callback with a new configure_filter() callback that takes
      filter flags (FIF_*) instead of interface flags (IFF_*).
      For a driver, this means it should open the filter as much
      as necessary to get all frames requested by the filter flags.
      Accordingly, the filter flags are named "positively", e.g.
      Multicast filtering is a bit special in that drivers that
      have no multicast address filters need to allow multicast
      frames through when either the FIF_ALLMULTI flag is set or
      when the mc_count value is positive.
      At the same time, drivers are no longer notified about
      monitor interfaces at all, this means they now need to
      implement the start() and stop() callbacks and the new
      change_filter_flags() callback. Also, the start()/stop()
      ordering changed, start() is now called *before* any
      add_interface() as it really should be, and stop() after
      any remove_interface().
      The patch also changes the behaviour of setting the bssid
      to multicast for scanning when IEEE80211_HW_NO_PROBE_FILTERING
      is set; the IEEE80211_HW_NO_PROBE_FILTERING flag is removed
      and the filter flag FIF_BCN_PRBRESP_PROMISC introduced.
      This is a lot more efficient for hardware like b43 that
      supports it and other hardware can still set the BSSID
      to all-ones.
      Driver modifications by Johannes Berg (b43 & iwlwifi), Michael Wu
      (rtl8187, adm8211, and p54), Larry Finger (b43legacy), and
      Ivo van Doorn (rt2x00).
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarMichael Wu <flamingice@sourmilk.net>
      Signed-off-by: default avatarLarry Finger <Larry.Finger@lwfinger.net>
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Ivo van Doorn's avatar