[pulseaudio-discuss] [alsa-devel] ASoC and pulseaudio
Liam Girdwood
liam.r.girdwood at linux.intel.com
Tue Mar 15 10:48:17 UTC 2016
On Tue, 2016-03-15 at 10:00 +0000, Mark Brown wrote:
> On Tue, Mar 15, 2016 at 09:48:51AM +0000, Liam Girdwood wrote:
> > On Tue, 2016-03-15 at 09:55 +0100, Takashi Iwai wrote:
>
> > > > Shouldn't we use whatever we use to figure out which firmware to load
> > > > rather than the firmware name? Someone might do something like try to
> > > > replace one firmware with another and get everything confused.
>
> > This is not to load FW for our use case, the FW name is hard coded in
>
> It's not for loading, it's because the firmware name we requested may
> not be the firmware that actually got loaded.
>
> > driver tables. We do have several FWs for the BYT driver that all have
> > different capabilities. Userspace could set the correct config for each
> > FW if it knew the FW that was being used.
>
> Is the firmware configuration sufficiently reusable between boards or
> could that just be figured out in userspace?
This depends on the FW. Some are quite reusable (i.e. use SSP0 instead
of SSP1), but others have could require additional config. This should
not be a problem for the newer FWs though that use topology though.
Liam
More information about the pulseaudio-discuss
mailing list