roadrunner2

FYI: on my MBP13,3, with the dGPU disabled (via switcheroo), I see about 8.7W - 9W usage with the display off, or about 12W at 50% brightness. I also see...

FYI, I figured out a fix for the excessive GPE interrupts (that were consuming ~ 58% cpu with recent kernels on my laptop) - see [my patch](https://bugzilla.kernel.org/attachment.cgi?id=278287) on [bug 198169](https://bugzilla.kernel.org/show_bug.cgi?id=198169).

@Ninlives Thanks for testing and reporting back.

@peterychuang, @whot: work is being done right now to get some core acpi support mainlined, and I think the aim is definitely to get this module get mainlined in the...

I've occasionally seen this corrupted packet too, but very rarely. However, looking at my dmesg on 5.4 I do see more of them too, so it looks like something changed...

Ok, thanks for the update. Btw., you can safely enable tracing of crc errors anyway, as that has no impact in the absence of errors and negligible impact even when...

Are there no other related messages before this? In particular, I'd expect some read error to be logged (most likely a bad-crc error). I've just fixed an issue with reading...

Apologies for the typo, and for not testing the kernel-command line instructions I gave. > > Are there no other related messages before this? In particular, I'd expect some read...

Sorry about the confusion: yes, I re-ordered the commits a bit, so it's not a fast-forward pull anymore, but you need not blow away the repo, just add the `--force`...

Please elaborate on "won't work": what exactly isn't working? The keyboard? The touchbar? Something else? A lot of information, btw, can be found at https://github.com/Dunedan/mbp-2016-linux/issues/ . Regarding the keyboard/trackpad driver...