1. 17 10月, 2006 2 次提交
  2. 28 7月, 2006 1 次提交
    • D
      [PATCH] softmac: ERP handling and driver-level notifications · 5acd0c41
      Daniel Drake 提交于
      This patch implements ERP handling in softmac so that the drivers can support
      protection and preambles properly.
      
      I added a new struct, ieee80211softmac_bss_info, which is used for
      BSS-dependent variables like these.
      
      A new hook has been added (bssinfo_change), which allows the drivers to be
      notified when anything in bssinfo changes.
      
      I modified the txrates_change API to match the bssinfo_change API. The
      existing one is a little messy and the usefulness of providing the old rates
      is questionable (and can be implemented at driver level if really necessary).
      No drivers are using this API (yet), so this should be safe.
      Signed-off-by: NDaniel Drake <dsd@gentoo.org>
      Acked-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      5acd0c41
  3. 22 7月, 2006 1 次提交
  4. 06 7月, 2006 1 次提交
    • L
      [PATCH] 2.6.17 missing a call to ieee80211softmac_capabilities from ieee80211softmac_assoc_req · 6d41e265
      Larry Finger 提交于
      In commit ba9b28d1, routine
      ieee80211softmac_capabilities was added to ieee80211softmac_io.c. As
      denoted by its name, it completes the capabilities IE that is
      needed in the associate and reassociate requests sent to the
      AP. For at least one AP, the Linksys WRT54G V5, the capabilities
      field must set the 'short preamble' bit or the AP refuses to
      associate. In the commit noted above, there is a call to the
      new routine from ieee80211softmac_reassoc_req, but not from
      ieee80211softmac_assoc_req. This patch fixes that oversight.
      
      As noted in the subject, v2.6.17 is affected. My bcm43xx card had been
      unable to associate since I was forced to buy a new AP. I finally was
      able to get a packet dump and traced the problem to the capabilities
      info. Although I had heard that a patch was "floating around", I had
      not seen it before 2.6.17 was released. As this bug does not affect
      security and I seem to have the only AP affected by it, there should
      be no problem in leaving it for 2.6.18.
      Signed-Off-By: NLarry Finger <Larry.Finger@lwfinger.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      6d41e265
  5. 06 6月, 2006 3 次提交
  6. 20 4月, 2006 1 次提交
  7. 23 3月, 2006 3 次提交