On 03/21/2012 10:03 AM, Peter Ujfalusi wrote:
On 03/20/2012 06:20 PM, Jarkko Nikula wrote:
I don't think this is going to solve the actual problem here where custom asound.conf was required.
I also suggested to use custom asound.conf. For Pandora it does exist, but the argument was that it need to be specifically created/copied to any new OS being ported to the HW.
IMHO custom sysfs is even worse option and very hard to remove afterwards.
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'm half thinking shall we leave this broken if we cannot figure out any automatic kernel based sulution to this?