1. 28 11月, 2017 1 次提交
  2. 30 10月, 2017 1 次提交
  3. 02 9月, 2017 1 次提交
  4. 27 11月, 2016 1 次提交
  5. 20 9月, 2016 3 次提交
  6. 20 11月, 2015 4 次提交
  7. 26 10月, 2015 1 次提交
  8. 24 9月, 2015 1 次提交
  9. 18 9月, 2015 1 次提交
  10. 17 9月, 2015 1 次提交
  11. 09 6月, 2015 1 次提交
  12. 02 4月, 2015 1 次提交
    • J
      Bluetooth: Add second hci_request callback option for full skb · e6214487
      Johan Hedberg 提交于
      This patch adds a second possible callback for HCI requests where the
      callback will receive the full skb of the last successfully completed
      HCI command. This API is useful for cases where we want to use a request
      to read some data and the existing hci_event.c handlers do not store it
      e.g. in the hci_dev struct.
      
      The reason the patch is a bit bigger than just adding the new API is
      because the hci_req_cmd_complete() functions required some refactoring
      to enable it: now hci_req_cmd_complete() is simply used to request the
      callback pointers if any, and the actual calling of them happens from a
      single place at the end of hci_event_packet(). The reason for this is
      that we need to pass the original skb (without any skb_pull, etc
      modifications done to it) and it's simplest to keep track of it within
      the hci_event_packet() function.
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      e6214487
  13. 31 3月, 2015 2 次提交
  14. 18 3月, 2015 1 次提交
  15. 15 3月, 2015 2 次提交
  16. 07 3月, 2015 1 次提交
  17. 03 3月, 2015 1 次提交
  18. 02 3月, 2015 2 次提交
  19. 12 1月, 2015 1 次提交
  20. 24 9月, 2014 1 次提交
  21. 15 9月, 2014 1 次提交
  22. 03 7月, 2014 1 次提交
  23. 13 2月, 2014 1 次提交
    • M
      Bluetooth: Introduce requirements for security level 4 · 7b5a9241
      Marcel Holtmann 提交于
      The security level 4 is a new strong security requirement that is based
      around 128-bit equivalent strength for link and encryption keys required
      using FIPS approved algorithms. Which means that E0, SAFER+ and P-192
      are not allowed. Only connections created with P-256 resulting from
      using Secure Connections support are allowed.
      
      This security level needs to be enforced when Secure Connection Only
      mode is enabled for a controller or a service requires FIPS compliant
      strong security. Currently it is not possible to enable either of
      these two cases. This patch just puts in the foundation for being
      able to handle security level 4 in the future.
      
      It should be noted that devices or services with security level 4
      requirement can only communicate using Bluetooth 4.1 controllers
      with support for Secure Connections. There is no backward compatibilty
      if used with older hardware.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      7b5a9241
  24. 05 12月, 2013 1 次提交
  25. 22 10月, 2013 1 次提交
  26. 14 10月, 2013 3 次提交
  27. 02 10月, 2013 1 次提交
  28. 24 9月, 2013 1 次提交
  29. 19 9月, 2013 1 次提交
  30. 21 8月, 2013 1 次提交