1. 14 8月, 2009 2 次提交
  2. 05 8月, 2009 1 次提交
  3. 08 7月, 2009 1 次提交
  4. 11 6月, 2009 2 次提交
  5. 23 4月, 2009 2 次提交
  6. 06 3月, 2009 1 次提交
  7. 12 2月, 2009 1 次提交
  8. 30 1月, 2009 2 次提交
    • M
      b43: Dynamically control log verbosity · 060210f9
      Michael Buesch 提交于
      Dynamically control the log verbosity with a module parameter.
      This enables us to dynamically enable debugging messages (or disable
      info, warn, error messages) via module parameter or /sys/module/b43/parameters/verbose.
      
      This increases the module size by about 3k. But in practice it reduces the
      module size for the user, because some distributions ship the b43 module
      with CONFIG_B43_DEBUG set, which increases the module by about 15k.
      
      So with this patch applied, distributions should really _disable_ CONFIG_B43_DEBUG.
      There is no reason to keep it in a production-release kernel.
      So we have a net reduction in size by about 12k.
      
      This patch also adds a printk of the wireless core revision, so people
      don't have to enable SSB debugging to get the wireless core revision.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      060210f9
    • M
      b43: Automatically probe for opensource firmware · 1a9f5093
      Michael Buesch 提交于
      First probe for proprietary firmware and then probe for opensource firmware.
      This way around it's a win-win situation.
      1) If proprietary fw is available, it will work.
      2) If opensource firmware is available, but no proprietary (Distros can only ship open fw)
         it might work.
      3) If both open and proprietary are available, it will work, because it selects
         the proprietary. We currently don't prefer the open fw in this case, because it doesn't
         work on all devices. It would introduce a regression otherwise.
      
      The remaining FIXMEs in this patch are harmless, because they only matter on multiband
      devices, which are not implemented yet anyway.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      1a9f5093
  9. 11 11月, 2008 1 次提交
  10. 16 9月, 2008 1 次提交
  11. 12 9月, 2008 1 次提交
  12. 30 8月, 2008 2 次提交
    • M
      b43: Rewrite TX power adjustment · 18c8adeb
      Michael Buesch 提交于
      This patch rewrites the TX power recalculation algorithms to scale better
      with changed enviromnent. If there's low
      TX traffic, the power will be checked against the desired values
      every 60 seconds.
      If there is high TX traffic, the check is redone every 2 seconds. This improves
      the reaction times a lot and confuses the rate control less.
      It will also reduce the time it initially takes to tune to a new TX power
      value. With the old algorithm it could take about 30 to 45 seconds to settle to
      a new power value. This will happen in about two to four seconds now.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      18c8adeb
    • M
      b43: Implement dynamic PHY API · ef1a628d
      Michael Buesch 提交于
      This patch implements a dynamic "ops" based PHY API.
      This is needed in order to conveniently support future PHY types
      to avoid the "switch"-hell.
      
      This patch does not change any functionality. It just moves lots
      of code from one place to another and adjusts it for the changed
      data structures.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      ef1a628d
  13. 27 6月, 2008 1 次提交
  14. 14 6月, 2008 1 次提交
  15. 29 5月, 2008 1 次提交
  16. 22 5月, 2008 5 次提交
  17. 15 5月, 2008 1 次提交
  18. 08 5月, 2008 1 次提交
  19. 02 5月, 2008 1 次提交
  20. 09 4月, 2008 5 次提交
  21. 08 3月, 2008 2 次提交
  22. 01 3月, 2008 3 次提交
  23. 16 2月, 2008 1 次提交
    • M
      b43: Add driver load messages · 26bc783f
      Michael Buesch 提交于
      This adds printk messages with basic information about the driver being loaded.
      This information includes a summary of the compiled-in features, which
      simplifies bug-reporting and debugging a lot.
      Also a firmware ID is printed. This is a unique identifier blob for a specific
      version of the firmware. This ID is attached to a specific version of the firmware
      blob in b43-fwcutter (see fwcutter git).
      This helps users to select the right firmware for their device.
      This also makes it possible to use automated scripts to fetch and extract the right
      firmware for the driver. (the script will grep the .ko for the "Firmware-ID: xxx" string.
      While the driver might still support other versions of the firmware for backward
      compatibility, this will always print out the officially supported version, which
      people _should_ use.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      26bc783f
  24. 06 2月, 2008 1 次提交