At Fri, 6 Oct 2006 15:34:30 +0200 (CEST), Jaroslav Kysela wrote: > > On Fri, 6 Oct 2006, Takashi Iwai wrote: > > > At Fri, 6 Oct 2006 15:19:58 +0200 (CEST), > > Jaroslav Kysela wrote: > > > > > > On Fri, 6 Oct 2006, Takashi Iwai wrote: > > > > > > > > > > BTW: Shouldn't all(?) these proc files eventually go to sysfs? > > > > > > > > > > > > There is already a function to add a sysfs file > > > > > > (snd_add_device_sysfs_file()), so it must be pretty easy. > > > > > > > > > > Yes and no. An layer for concrete device/substream should be added. > > > > > > > > Right, it's missing. > > > > > > > > > Anyway, actually we can move most of values from proc to sysfs for 2.6. > > > > > Any problems with it? > > > > > > > > Proc files for showing information are OK, but controlling the driver > > > > over proc file isn't a recommended way on 2.6 kernel. That's what > > > > sysfs is for. > > > > > > > > Anyway it's no big deal but just TODO. > > > > > > I'd like to create similar layer as in proc, but it seems that we must > > > place cards root somewhere. Do you think that /sys/class/soundcard is good > > > place and name for this root? > > > > I don't think so. /sys/class are referred by HAL to probe the device > > files. Adding a root would simply confuse the system. > > Hmm. Any suggestion? /sys/bus or /sys/devices does not seem also as a > right place. We can create another class for the sound-root. But, better to ask sysfs guys before starting working on it. Alternatively, we can put the tree under controlC* entry since control is corresponding to each card in ALSA. Actually, snd_card instance is _the_ container of control elements. Takashi ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
