Documentation request: interpreting Bluetooth traces for controller identification

[Raton-Laveur]

Related to section 9: Bluetooth HCI trace with Win10

Documentation is provided for getting traces, but not on how to interpret them in order to patch in a new controller.

Currently, @darthcloud is pretty much the only dev that can grok controller traces, then add a new controller.

As many Bluetooth controllers exist, providing documentation to add them might reduce your issue workload if other contributors know how to patch in those they own.

[darthcloud]

Right now the tooling to parse the trace (under tests folder of main repo) is not very robust.

And that tooling is only useful if the problem is located in the hid_parser module.

What I have found after receiving trace for over a year+ is that issue are rarely in the hid_parser anymore.

The trace could be useful still but it would need adding injection hooks in the code and making new script to inject the packets from the trace.

This is a lot of work.

It would certainly be a good investment long term but in the short term I got very little time so I try to mostly go through the bugs reported.