diff options
| author | stig <stig@f5534014-38df-0310-8fa8-9805f1628bb7> | 2008-02-03 21:11:53 +0000 |
|---|---|---|
| committer | stig <stig@f5534014-38df-0310-8fa8-9805f1628bb7> | 2008-02-03 21:11:53 +0000 |
| commit | bf9fc6d8fca2bb4e7bdbfb44e9177530146cf7f9 (patch) | |
| tree | 3be42b7d6cdeb7cb033fa3ed154293a6d37d6a40 /doxygen_global.cfg | |
| parent | 57f58e6affaecb2bf29a69ce903d14541aebb3dc (diff) | |
From Shane Kearns (bug 2237):
Added support for Symbian OS btsnoop.
The bluetooth HCI layer in Symbian OS can be configured to log all packets to a
file. The log format, "btsnoop" is based on the RFC1761 "snoop" format - but
differences in the header make it incompatible.
The btsnoop format supports logging of these formats:
"H1" (raw HCI packets without framing)
"H4" (HCI UART packets including packet type header)
"H5" (HCI 3 wire UART packets including framing)
"BCSP" (HCI bluecore serial protocol including framing)
"H1" and "H4" are section numbers in the original v1 bluetooth specifications,
but still used colloquially - wireshark's existing support for Linux bluez HCI
logs uses the "H4" name.
In practice, the "H1" format is used for H5,BCSP and USB HCI logs, as the HCI
packet logs are mainly useful for debugging higher layers, bluetooth profiles
and bluetooth applications.
From me:
Deleted some unused prototypes.
Mark an unused parameter.
git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@24263 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'doxygen_global.cfg')
0 files changed, 0 insertions, 0 deletions