[alsa-devel] Neverending HDA pin quirks, how does Windows cope?
Hi,
We're constantly having to support new laptop models from vendors and the majority of them always seem to need some kind of HDA quirk adding, especially for pin usage info where the BIOS data is clearly incorrect. From the vast collection of quirks present in Linux's HDA drivers I see we are not alone.
We're trying to figure out if there is a way the BIOS can be fixed for the cases that come from our partners, but I am also curious as to how this is managed on Windows and if we can learn anything from that.
I had a look at the windows driver for some affected hardware. I was unable to identify any hardware-specific quirks in the .inf files, but using "strings" I found that various binary .sys, .dll and .dat files refer to hundreds of different laptop models.
That might suggest that for each new laptop model, they make a modification to the windows driver, recompile, and get the new version signed again by MS? Sounds insane, anyone know for sure how this is handled?
Thanks Daniel
participants (1)
-
Daniel Drake