1. 12 Jun, 2009 4 commits
  2. 11 Jun, 2009 3 commits
  3. 06 Jun, 2009 1 commit
  4. 05 Jun, 2009 4 commits
  5. 03 Jun, 2009 1 commit
  6. 02 Jun, 2009 1 commit
  7. 01 Jun, 2009 1 commit
  8. 21 May, 2009 1 commit
  9. 20 May, 2009 6 commits
  10. 19 May, 2009 2 commits
    • Bastien Nocera's avatar
      bluetooth: fixes for NMManager bluetooth device handling · c67aace3
      Bastien Nocera authored
      - Re-query the BlueZ manager when connection, or connections are
        added
      - Don't assert when a new BT device is created
      - Fix the connection bdaddr and device bdaddr comparison, we
        were comparing a byte array with a string
      - Simplify bluez_manager_bdaddr_has_connection()
      c67aace3
    • Bastien Nocera's avatar
      bluetooth: fixes for NMDeviceBt · b2305fcb
      Bastien Nocera authored
      - Use NM_BT_CAPABILITY_NONE instead of 0 when appropriate
      - Don't assert on priv->bt_type not being set in
        real_deactivate_quickly(), as it might be called with no
        connections activated
      - Fix cut'n'paste typo that made setting the device capabilities
        assert
      b2305fcb
  11. 18 May, 2009 4 commits
  12. 15 May, 2009 1 commit
  13. 14 May, 2009 7 commits
  14. 13 May, 2009 3 commits
    • Dan Williams's avatar
      bluetooth: add NMSettingBluetooth · 4ab96e8e
      Dan Williams authored
      4ab96e8e
    • Dan Williams's avatar
      wifi: 64-bit compile warning fix · 0e3cdd61
      Dan Williams authored
      0e3cdd61
    • Dan Williams's avatar
      wifi: handle unsolicited supplicant scans · 57a04fa5
      Dan Williams authored
      With supplicant patches, this allows NM to figure out when the supplicant
      is performing an unsolicited scan, and thus to not run periodic_update()
      when the supplicant is scanning.
      
      This fixes some of the causes of "roaming to none", especially in hidden
      SSID networks.  In those cases, after NM had requested a broadcast scan,
      the hidden SSID AP would likely not show up in the scan results, leading
      to the supplicant performing a specific SSID scan that NetworkManager
      was unaware of.  While that specific SSID scan was going on, NM could
      run periodic_update() and pull the wrong frequency off the card,
      leading to the "roaming to none" message when the associated AP with
      the wrong frequency could not be found in the scan list.
      57a04fa5
  15. 12 May, 2009 1 commit