Hacker News new | past | comments | ask | show | jobs | submit login

Perhaps someone could just reverse engineer what the Windows driver does to get the values.

It could be a nice way to learn a tool like Binary Ninja or IDA (pro).

It's probably some DeviceIoControl call. Once you know the call 12-bit (I think?) ID from userland code, it should be relatively straightforward to follow the driver code to see where it ends up and what hardware registers it uses.

Or maybe it's just something through ACPI?

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact