21 Mar
2012
21 Mar
'12
9:40 a.m.
On Wed, Mar 21, 2012 at 10:32:11AM +0200, Jarkko Nikula wrote:
On 03/21/2012 10:03 AM, Peter Ujfalusi wrote:
Well, for system integration's point of view I would prefer the sysfs file. If this is needed by the distribution/use case it can be enabled, disabled in runtime. In my view it poses less hassle for distributions.
Problem with custom sysfs is that no generic distribution is going to use it but problem can be triggered there. IMHO for tailored distribution point of view custom sysfs setting is no better than custom asound.conf.
I have to say that I agree wholeheartedly with this - the sysfs rule has all the problems that a custom asound.conf does.