On Sun, 16 Jul 2006, Berndt Josef Wulf wrote:

> I then increased the debug level for net.bluetooth.debug = 15 and now get a
> few extra debug messages:

and hw.ubt_debug=15 also please?

> Jul 16 19:52:18  /netbsd: hci_usrreq: ATTACH
> Jul 16 19:52:18  /netbsd: hci_usrreq: CONTROL
> Jul 16 19:52:18  /netbsd: hci_ioctl: cmd 0xc0386205
> Jul 16 19:52:18  /netbsd: hci_usrreq: CONTROL
> Jul 16 19:52:18  /netbsd: hci_ioctl: cmd 0xc0386208
> Jul 16 19:52:18  /netbsd: ubt_enable: sc=0xc1f89400
> Jul 16 19:52:18  /netbsd: hci_send_cmd: (ubt0) opcode (004|0009)
> Jul 16 19:52:18  /netbsd: hci_output_cmd: (ubt0) num_cmd_pkts=1
> Jul 16 19:52:18  /netbsd: hci_send_cmd: (ubt0) opcode (004|0005)
> Jul 16 19:52:18  /netbsd: hci_send_cmd: (ubt0) opcode (004|0003)
> Jul 16 19:52:18  /netbsd: hci_intr: (ubt0) recv event, len = 13
> Jul 16 19:52:18  /netbsd: hci_event: (ubt0) event COMMAND COMPLETE
> Jul 16 19:52:18  /netbsd: hci_event_command_compl: (ubt0) opcode (004|0009)
> num_cmd_pkts = 1
> Jul 16 19:52:18  /netbsd: hci_output_cmd: (ubt0) num_cmd_pkts=1
> Jul 16 19:52:18  /netbsd: hci_intr: done

though this does show that the second command is taken from the queue and
sent to the device (hci_output_cmd) after the COMMAND_COMPLETE which does
place it in the domain of USB somewhere.

iain