Yatao Li
Just checked the module. le32 indeed no problem.
Let me check if profile get can return the correct answer. If so, the problem may be somewhere else?
Yeah, I just checked. Performance profile readback is correct. The capture log is a huge stream of category 21(0x15) plus these two 0x03, and a few 0x01. Maybe I should...
oh and this: `warning: expected SYN, skipping data until next SYN`
With only cat 21 filtered: ```json {"ctrl": {"type": 128, "len": 12, "pad": 0, "seq": 42}, "cmd": {"type": 128, "tc": 3, "outgoing": 1, "incoming": 0, "iid": 0, "rqid_lo": 83, "rqid_hi": 3,...
The bug is caused probably because IRPComp piggyback'ed another HID message This is message 42: ``` ID = 103109 Time = 2/18/2022 7:02:29 PM Type = IRP Device object =...
Any ideas on the BKL message? It could be a random coincidence but intriguing :p
Makes sense, could be backlight related stuff since I'm adjusting power profiles. I'm wondering if the module handles the piggybacks and incomplete frames?
aha. pretend we are 0x17 experts. 😎
By piggyback I mean, for example in this reply: ``` 00: aa 55 40 00 00 2a 74 6f ff ff aa 55 00 26 00 df ªU@..*toÿÿªU.&.ß 10: 34...