At Tue, 15 Jan 2008 13:23:52 -0800, Tobin Davis wrote:
Actually, if this were done correctly, it would use the /sys file system for configuration changes. /proc should be read only space.
As it sits now, you should be able to change the model configuration by typing "echo <model> /sys/module/snd_hda_intel/parameters/model", but I don't think it's setup to dynamic changing yet. The /proc/asound/card0/codec# file contains all of the connection configurations for each codec NID. With that and the model diagram from most vendors, it would be easy to reconfigure on the fly.
The dynamic model change isn't too difficult to implement. But, this alone wouldn't be helpful. It's nothing but reloading the module with a different module option.
The problem is how to pass the proper data *before* setting up the device. So far, the device probe routine is called when the driver is loaded.
Takashi
On Tue, 2008-01-15 at 21:08 +0100, Marco Schuster wrote:
Andrew Paprocki schrieb:
Could this all be done through a /proc interface? For example, a /proc/asound/hda directory which contained files representing the different connections in the chipset?
/proc isn't constant, right? Marco
PS: Is it usual here to CC all people on the thread?
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
-- Tobin Davis
Memory should be the starting point of the present. _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel