[alsa-devel] Shipping UCM configuration files in upstream alsa-lib
Hi,
It seems that there are no UCM configuration files in the alsa-lib tarball (or am I not looking hard enough?). Has it been decided that alsa-lib should not ship with UCM configuration files, or is it just that nobody has so far submitted such files for inclusion? I'm about to start learning about UCM by writing some configuration files for the Nokia N900, and I'd like to get those files eventually to upstream.
I think it makes sense to ship the UCM files in upstream, because that way when you port a new Linux distribution on a piece of hardware, there's a better chance for audio to "just work". And even if Mer (which I'm using) will be the only distribution that is going to be interested in the UCM files for N900, Mer can avoid maintaining any patches on top of alsa-lib if everything is in upstream.
At Mon, 30 Jul 2012 11:38:52 +0300, Kaskinen Tanu wrote:
Hi,
It seems that there are no UCM configuration files in the alsa-lib tarball (or am I not looking hard enough?). Has it been decided that alsa-lib should not ship with UCM configuration files, or is it just that nobody has so far submitted such files for inclusion?
I think it's the latter.
I'm about to start learning about UCM by writing some configuration files for the Nokia N900, and I'd like to get those files eventually to upstream.
I think it makes sense to ship the UCM files in upstream, because that way when you port a new Linux distribution on a piece of hardware, there's a better chance for audio to "just work". And even if Mer (which I'm using) will be the only distribution that is going to be interested in the UCM files for N900, Mer can avoid maintaining any patches on top of alsa-lib if everything is in upstream.
Yeah, I find it'd be useful, too.
thanks,
Takashi
participants (2)
-
Kaskinen Tanu
-
Takashi Iwai