Unable to find an usable access for 'default' aplay: set_params:832: Sample format non
available
Yes. Thanks for your replay. Maybe I should send the mail to arm-linux mailist.
PS. Could you recommend some docs about the ALSA internals and Low level drivers? There are too many docs in the www.alsa-project.org, I am an embedded Linux driver developer, so which one is suit for me?
Thanks a lot Best Regards
The useful developer docs seem to have been lost off the alsa web server.
From: http://www.alsa-project.org/documentation.php3#Driver, there are the following broken links:
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/index.html
http://www.alsa-project.org/~iwai/alsa-driver-api/index.html
When you build a new alsa driver, you generally have to also create a /usr/share/alsa/cards/XXX file, where XXX is the name of your driver.
The XXX comes from either: - strcpy(card->driver, "XXX"); in your probe routine.
I think you will find the most help if you post the unfinished source code for your driver, so that people can look at it, and maybe suggest corrections for you.
The best way to test your new driver is with a test tool like speaker-test or pcm.
With these you can send a tone to the speakers. You can also set the sample rate and number of channels, so that it can test the driver, without needing to use plug devices initially.
E.g. If your sound card can only do 48khz stereo. Start testing it with:
speaker-test -r48000 -Dhw:0,0 -c2
plug devices tend not to work well until you have a correctly functioning driver.
Cheers James
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
