Yeah,.., I feel familiar with that method -:) I guess I'm not the only one
I've been trying to debug the driver, but it's not really my thing... Maybe there are some handy tricks to debug ALSA drivers? Or is it just:
1) change the source
2) compile the source
3) see if it works (by loading the module.. and playing some audio)
4) if it doesn't work restart with 1)
Probably you can add a point:
3.5) If the computer totally freezes (course change to the source was very wrong and bad) restart computer, and go to 1) + (I hate ext2 filesystems)
I don't known any better method, maybe just yet another point:
1.5) review changes yet one more time and go back to 1 or 1.5 a couple of times
to try prevent moment "3.5"
But, stuffs like the tool "ksymoops", the alsa functions/macros: snd_assert(...),
snd_magic_cast(...), snd_printk(...), snd_printdd(...), etc. helps a lot!
/Benny
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
