Maximilian Luz

Also interesting, it's right [there](https://gist.github.com/kitakar5525/7221bd545cbea68ef228ef8d9071b4d5#file-dsdt-dsl-L16346) in the DSDT that it communicates via HID: ``` Name (_CID, "PNP0C50" /* HID Protocol Device (I2C bus) */) // _CID: Compatible ID ``` Also...

With one of Alex' slides and the HID-over-I2C spec I think I've figured out the buffer that is being sent (it's indeed valid HID-over-I2C): - `BE EF` probably the address,...

Ah yeah, `PNP0C50` is the compatibility ID (`_CID`) the actual device ID is `MSHW0030`. It's probably not visible in `/dev/input` and `/dev/hidraw` because the OperationRegion handler on the parent device...

Might make a difference, to be honest I can't say.

> If we need report descriptor of detach/dGPU related thing, maybe we can get it on Windows by another way instead of IRPMon/DebugView. That's probably an option, but I'm not...

Awesome work! I'm a bit busy at the moment, so I've only had a quick look over the logs, but it seems like this is everything we needed! I think...

Wow, that's some good progress! Sorry I've been absent for a while (had some exams), I'll try to have a look at it this evening. If I understand you correctly,...

Just for the record: The HID vendor/ID of the SAM device is `045E:0914`.

Okay, I've uploaded an initial driver [here](https://github.com/qzed/linux-surface-sam-hid). It doesn't send the I2C messages yet, but it should show some output in the dmesg log. Can you check if those messages...

Okay, thanks guys! I'll try to figure out why the address-space handler can't be installed.