On Tue, Aug 27, 2019 at 12:18:12PM -0500, Pierre-Louis Bossart wrote: > Mark suggested: > "We could have a wrapper which tries to load the newer firmware and uses > the fixed driver code if that's there, otherwise tries the old driver > with the existing firmware paths." > Maybe that's too complicated, I had in mind some sort of opt-in Kconfig > where you only use the new firmware/topology when the user/distro gives a > clear hint than it's fine to use newer stuff. To be clear I don't think this is a *good* idea, but I'm not sure that there are any options that are good ideas. > I also wonder how you are going to deal with all these topology files with a > name derived from the OEM/NHLT. There's just so many of them...For upstream > you probably want to provide ONE per platform variant, which limits you to > the number of machine drivers supported. Unless the way they're generated is consistent (or often consistent) in which case you can just derive it?
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
