1. 20 2月, 2012 6 次提交
  2. 13 2月, 2012 1 次提交
  3. 03 1月, 2012 1 次提交
  4. 20 12月, 2011 1 次提交
  5. 19 12月, 2011 4 次提交
  6. 21 9月, 2011 1 次提交
    • A
      Bluetooth: Add mgmt events for blacklisting · 5e762444
      Antti Julku 提交于
      Add management interface events for blocking/unblocking a device.
      Sender of the block device command gets cmd complete and other
      mgmt sockets get the event. Event is also sent to mgmt sockets when
      blocking is done with ioctl, e.g when blocking a device with
      hciconfig. This makes it possible for bluetoothd to track status
      of blocked devices when a third party block or unblocks a device.
      
      Event sending is handled in mgmt_device_blocked function which gets
      called from hci_blacklist_add in hci_core.c. A pending command is
      added in mgmt_block_device, so that it can found when sending the
      event - the event is not sent to the socket from which the pending
      command came. Locks were moved out from hci_core.c to hci_sock.c
      and mgmt.c, because locking is needed also for mgmt_pending_add in
      mgmt.c.
      Signed-off-by: NAntti Julku <antti.julku@nokia.com>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      5e762444
  7. 17 6月, 2011 1 次提交
  8. 22 2月, 2011 1 次提交
    • A
      Bluetooth: fix build break on hci_sock.c · b7440a14
      Anand Gadiyar 提交于
      Linux-next as of 20110217 complains when building for OMAP1.
      
        LD      vmlinux
      `hci_sock_cleanup' referenced in section `.init.text' of net/built-in.o: defined in discarded section `.exit.text' of net/built-in.o
      `hci_sock_cleanup' referenced in section `.init.text' of net/built-in.o: defined in discarded section `.exit.text' of net/built-in.o
      make: *** [vmlinux] Error 1
      
      A recent patch by Gustavo (Bluetooth: Merge L2CAP and SCO modules
      into bluetooth.ko) introduced this by calling the hci_sock_cleanup
      function in the error path of bt_init.
      
      Fix this by dropping the __exit marking for hci_sock_cleanup.
      Signed-off-by: NAnand Gadiyar <gadiyar@ti.com>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      b7440a14
  9. 08 2月, 2011 1 次提交
  10. 23 12月, 2010 1 次提交
  11. 08 12月, 2010 2 次提交
  12. 02 12月, 2010 1 次提交
  13. 01 8月, 2010 1 次提交
  14. 22 7月, 2010 1 次提交
  15. 28 2月, 2010 1 次提交
  16. 04 12月, 2009 2 次提交
  17. 06 11月, 2009 1 次提交
  18. 07 10月, 2009 1 次提交
  19. 01 10月, 2009 1 次提交
  20. 30 11月, 2008 1 次提交
  21. 15 7月, 2008 1 次提交
    • M
      [Bluetooth] Export details about authentication requirements · 40be492f
      Marcel Holtmann 提交于
      With the Simple Pairing support, the authentication requirements are
      an explicit setting during the bonding process. Track and enforce the
      requirements and allow higher layers like L2CAP and RFCOMM to increase
      them if needed.
      
      This patch introduces a new IOCTL that allows to query the current
      authentication requirements. It is also possible to detect Simple
      Pairing support in the kernel this way.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      40be492f
  22. 03 5月, 2008 1 次提交
  23. 29 3月, 2008 1 次提交
  24. 06 3月, 2008 1 次提交
  25. 01 11月, 2007 1 次提交
  26. 22 10月, 2007 1 次提交
    • M
      [Bluetooth] Switch from OGF+OCF to using only opcodes · a9de9248
      Marcel Holtmann 提交于
      The Bluetooth HCI commands are divided into logical OGF groups for
      easier identification of their purposes. While this still makes sense
      for the written specification, its makes the code only more complex
      and harder to read. So instead of using separate OGF and OCF values
      to identify the commands, use a common 16-bit opcode that combines
      both values. As a side effect this also reduces the complexity of
      OGF and OCF calculations during command header parsing.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      a9de9248
  27. 11 10月, 2007 1 次提交
    • E
      [NET]: Make socket creation namespace safe. · 1b8d7ae4
      Eric W. Biederman 提交于
      This patch passes in the namespace a new socket should be created in
      and has the socket code do the appropriate reference counting.  By
      virtue of this all socket create methods are touched.  In addition
      the socket create methods are modified so that they will fail if
      you attempt to create a socket in a non-default network namespace.
      
      Failing if we attempt to create a socket outside of the default
      network namespace ensures that as we incrementally make the network stack
      network namespace aware we will not export functionality that someone
      has not audited and made certain is network namespace safe.
      Allowing us to partially enable network namespaces before all of the
      exotic protocols are supported.
      
      Any protocol layers I have missed will fail to compile because I now
      pass an extra parameter into the socket creation code.
      
      [ Integrated AF_IUCV build fixes from Andrew Morton... -DaveM ]
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1b8d7ae4
  28. 12 9月, 2007 1 次提交
  29. 09 9月, 2007 2 次提交