[Bluetooth] Switch from OGF+OCF to using only opcodes

Browse Source

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>

...

This commit is contained in:

Marcel Holtmann

2007-10-20 13:33:56 +02:00

committed by David S. Miller

parent 55b70a0300

commit a9de924806

8 changed files with 1589 additions and 1306 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

884

include/net/bluetooth/hci.h

File diff suppressed because it is too large Load Diff