7 Mar
2018
7 Mar
'18
3:28 p.m.
On Wed, Mar 07, 2018 at 02:49:05PM +0100, Hans de Goede wrote:
Although I agree that ideally we would be able to get all this directly from the firmware, to me fixing the x86 specific problem of that info missing using quirks in the Intel machine driver seems like the right place to fix this, so that we are not "poluting" generic code with these Intel specific workarounds.
Yeah, my feeling here is that this is less pollution than you're seeing it as - it's too much like endorsement of the Windows one driver per machine way of doing things and splits the knowledge about how the device gets used about more. Purely a taste question.