Marcel Holtmann a9de924806 [Bluetooth] Switch from OGF+OCF to using only opcodes ... 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: Marcel Holtmann <marcel@holtmann.org>		2007-10-22 02:59:40 -07:00
..
bcm203x.c
bfusb.c
bluecard_cs.c
bpa10x.c
bt3c_cs.c
btuart_cs.c
dtl1_cs.c
hci_bcsp.c	[Bluetooth] Switch from OGF+OCF to using only opcodes	2007-10-22 02:59:40 -07:00
hci_h4.c
hci_ldisc.c
hci_uart.h
hci_usb.c	[Bluetooth] Add missing stat.byte_rx counter modification	2007-09-09 08:39:27 +02:00
hci_usb.h	[Bluetooth] Use hci_recv_fragment() within HCI USB driver	2007-07-11 06:42:35 +02:00
hci_vhci.c	[Bluetooth] Remove the redundant non-seekable llseek method	2007-07-11 06:53:45 +02:00
Kconfig
Makefile