>> i would personally work from a complete set of snd-* modules, and use >> modinfo(1) + perl to get the information > >Isn't that what happens in the INSTALL file anyway?
it doesn't look like it. there are several cards missing there, and it looks hand-written rather then fetched from the source. >> and put that into the temp >> file that is inserted into the template, or if possible, put it >> straight into the template. >> > >IIRC doing the above would need access to a set of modules online. Seems >unneccesary when the INSTALL file is already available. > >But I'm willing to be told otherwise if it makes the info more reliable. it would be much more reliable if you got the options from the modules themselves. even just running grep for MOD_PARM etc. would be better than using the INSTALL file. --p ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
