aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors/packet-hci_h1.c
Commit message (Collapse)AuthorAgeFilesLines
* The dissector does not use any bytes.Stig Bjørlykke2009-04-241-1/+1
| | | | svn path=/trunk/; revision=28142
* Add support for reading Apple's Bluetooth PacketLogger capture files toStephen Fisher2009-02-161-5/+30
| | | | | | | | wiretap. Modify various other locations to accommodate the fact that PacketLogger files do not specify the direction of packets. svn path=/trunk/; revision=27463
* Remove "empty" header fileStephen Fisher2009-02-031-1/+0
| | | | svn path=/trunk/; revision=27361
* From Shane Kearns (bug 2237):Stig Bjørlykke2008-02-031-0/+134
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. svn path=/trunk/; revision=24263