On Mon, Jun 12, 2017 at 4:53 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Sedat, > >> I have applied two patches from bluetooth-next... >> >> Bluetooth: Send HCI Set Event Mask Page 2 command only when needed >> Bluetooth: btbcm: Read controller features during configuration >> >> ...against the official Debian/stretch kernel v4.9.30. >> >> And grabbed a trace-log via 'btmon -w trace.log'. >> >> When doing a... >> >> btmon --read btmom-w_bcm20702_bth-next-fixed.BTSnoop-v1 >> >> ...I cannot see the lines with "Broadcom Read Controller Features". >> >> What am I doing wrong? > > you need a btmon from git that is capable of decoding it. > OK, I see. The 2nd patch is not helpful for me on Debian/stretch when I need to upgrade my userspace. > < HCI Command: Vendor (0x3f|0x006e) plen 0 >> HCI Event: Command Complete (0x0e) plen 12 > Vendor (0x3f|0x006e) ncmd 1 > Status: Success (0x00) > 07 00 00 00 00 00 00 00 > > Otherwise you are just seeing this. > >> How can I convert that BTsnoop-v1 binary log-file? >> Let's say ASCII. > > btmon -r trace.log > trace.txt > Thanks, that worked. >> More precisely I wanted to investigate if the list of local-supported >> HCI event commands matches/dismatches the list shown from the >> firmware. > Is there a general approach for this thought than using HCI_QUIRK_BROKEN_LOCAL_COMMANDS workaround (example patch from [1])? Regards, - Sedat - [1] https://www.spinics.net/lists/linux-bluetooth/msg70436.html -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
