On Mon, Oct 12, 2020 at 11:09:04AM +0200, Takashi Iwai wrote: > Hans de Goede wrote: > > replacement and dropping the old code ? I'm not sure if that is such > > a great idea, what is the fallback plan if testing does find significant > > issues with the new catpt code ? > I find the action a bit too rushing, too. OTOH, the old code wasn't > well maintained, honestly speaking. So, from another perspective, > switching to a new code can be seen as a better chance to fix any > bugs. That was my take as well - the old code seemed to be very fragile for structural reasons which are hopefully addressed here and Intel seem willing to actively work on supporting this version. I have to confess I had assumed Hans had seen all this stuff going past, the new driver got quite a few rounds of review. > Of course, we could keep two stuff parallel, but it's rather > confusing. And, the HSW/BDW devices that need SST are quite rare and > old, so the impact is limited, I guess. Yes, figuring out which of the various x86 audio driver options you need is fairly painful ATM. Worst case it's just a revert of this removal commit.
Attachment:
signature.asc
Description: PGP signature
