[Sound-open-firmware] Distribution of sof firmware and tplg files

[Jaroslav Kysela]

Dne 11. 01. 20 v 13:17 Pierre-Louis Bossart napsal(a):
> 
>> So basically, my proposal is:
>>
>> 1) create one source (tar ball file, repository tag) per SOF release
>>      - all things should be there (firmware, debug files, topologies)
>> 2) push stable / tested mainstream firmware files to linux-firmware
>>      - licencing / copyright
>> 3) push topology changes to alsa-topology-conf repo
>> 4) propose UCM fixes to alsa-ucm-conf repo if required for the updated
>>      topology files
> 
> I am sorry, you've lost me here.
> 
> If we push firmware through the linux-firmware tree, topology those
> alsa-topology-conf and UCM through alsa-ucm-conf, then who would be the
> users of the package 1)?
> 
> Conversely if people use item #1, then why should we care about 2) 3)
> and 4)?
> 
> I'd like to avoid duplication of work and potential misalignment between
> integration flows.

The all-in-one package is useful for:

1) debugging .ldc files - they don't belong to any of the upstream repos
2) SOF release - you have full control to put all things together and
    we can use this as a reference; eventually, we can update the community
    integration repos from this
3) extra firmware files (not used by default kernel configuration / code)

It does not mean that the stable code should not be pushed to the 
"integration" repositories (where the code is merged from the multiple 
sources). But in case of issues (debugging) or if you have special users 
(firmware for special hardware variants requiring the extra kernel parameters 
/ setup), the users might look back to the all-in-one repo (SOF project release).

I think that this will work for all of us.

					Jaroslav

-- 
Jaroslav Kysela <perex at perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.