I primarily looked at vbtn.asl (the other files seem sane I don't have a spec to reference).

I'm pretty sure that the Windows driver doesn't bother to check the chassis type (nor do anything else besides the required core functionality), so the Linux driver probably could've used a different workaround (or avoided one entirely). Regardless, there's not much we can do about unless/until someone can get their hands on the system that caused the kernel workaround to be introduced.

Patch set 4:Code-Review +1

To view, visit change 31208. To unsubscribe, or for help writing mail filters, visit settings.