Re: [Alsa-user] Getting a driver to support alsa natively
On 10/01/2008, Clemens Ladisch [EMAIL PROTECTED] wrote: Adrian McMenamin wrote: $ aplay -D hw:0,0 /aine-email.wav Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono aplay: set_params:895: Access type not available This means that the device does not support SND_PCM_ACCESS_RW_INTERLEAVED. According to pcm_native.c, this means that SNDRV_PCM_INFO_INTERLEAVED is not set: if (hw-info SNDRV_PCM_INFO_INTERLEAVED) mask |= 1 SNDRV_PCM_ACCESS_RW_INTERLEAVED; Could explain this a bit further? The driver doesn't support interleaved because the hardware doesn't. But I assume alsa-lib can fix that? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
Adrian McMenamin wrote: On 10/01/2008, Clemens Ladisch [EMAIL PROTECTED] wrote: Adrian McMenamin wrote: $ aplay -D hw:0,0 /aine-email.wav Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono aplay: set_params:895: Access type not available This means that the device does not support SND_PCM_ACCESS_RW_INTERLEAVED. Could explain this a bit further? The driver doesn't support interleaved because the hardware doesn't. But I assume alsa-lib can fix that? Not when using hw, but the plug plugin should be able to do this (when the access types don't match, it inserts the copy plugin). I don't know why this doesn't work when you're using plughw. Regards, Clemens - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On 10/01/2008, Clemens Ladisch [EMAIL PROTECTED] wrote: Adrian McMenamin wrote: On 10/01/2008, Clemens Ladisch [EMAIL PROTECTED] wrote: Adrian McMenamin wrote: $ aplay -D hw:0,0 /aine-email.wav Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono aplay: set_params:895: Access type not available This means that the device does not support SND_PCM_ACCESS_RW_INTERLEAVED. Could explain this a bit further? The driver doesn't support interleaved because the hardware doesn't. But I assume alsa-lib can fix that? Not when using hw, but the plug plugin should be able to do this (when the access types don't match, it inserts the copy plugin). I don't know why this doesn't work when you're using plughw. Well the issue is surely as to why aplay -l correctly reports the device but aplay -L reports only the null PCM - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
Adrian McMenamin wrote: Lee Revell wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. Done: http://hg.alsa-project.org/alsa-lib/rev/5593d06d30ee. Regards, Clemens - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On 09/01/2008, Clemens Ladisch [EMAIL PROTECTED] wrote: Adrian McMenamin wrote: Lee Revell wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. Done: http://hg.alsa-project.org/alsa-lib/rev/5593d06d30ee. OK, well that does throw up any (new) errors. So, whatever my issue is, I think I can assume it is not and never has been missing config files or a bad path them. Just as before: $ aplay -l List of PLAYBACK Hardware Devices card 0: AICA [AICA], device 0: AICA PCM [AICA PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ $ aplay -L null Discard all samples (playback) or generate zero samples (capture) $ $ aplay -D hw:0,0 /aine-email.wav Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono aplay: set_params:895: Access type not available $ $ aplay -D plughw:0,0 /aine-email.wav Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ALSA lib pcm_plug.c:773:(snd_pcm_plug_hw_refine_schange) Unable to find an usable access for 'plughw:0,0' aplay: set_params:895: Access type not available (Incidentally I also know that aplay is opening the driver) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On 06/01/2008, Jan-Benedict Glaw [EMAIL PROTECTED] wrote: Specifically for a NFS server that's handling development clients, I'd really suggest you to install the userland NFS server and strace it. That's a really easy solution to a lot of problems! Any clues as to how to get that to work? The daemon just dies on me (I am using rpc.nfsd) when I try to strace it - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On Sun, 2008-01-06 02:39:48 +0200, Sergei Steshenko [EMAIL PROTECTED] wrote: On Sun, 06 Jan 2008 00:24:11 + James Courtier-Dutton [EMAIL PROTECTED] wrote: Sergei Steshenko wrote: On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? Please file a bug - otherwise ALSA programmers will continue writing code which does not print full paths to files it tries to open. What is the problem? Just use: strace aplay -L 21 |grep open That will list all files being opened. The problem is the word all - I wanna see just the failing ones. strace aplay -L 21 | grep open | grep ENOENT And, IIRC, earlier in this or similar thread was stated that 'strace' wasn't working for ARM plarform. That's the actual problem. However, when I'm doing MIPS or VAX work, which I, too, do mostly with NFS root, there are a number of other solutions. You can sniff the network traffic (tcpdump/wireshark) to see what the client box is doing, or you can (this requires userspace NFS server instead of the faster kernel NFS server) strace the NFS server program. Specifically for a NFS server that's handling development clients, I'd really suggest you to install the userland NFS server and strace it. That's a really easy solution to a lot of problems! MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED] +49-172-7608481 Signature of: The course of history shows that as a government grows, liberty the second : decreases. (Thomas Jefferson) signature.asc Description: Digital signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Getting a driver to support alsa natively
Apologies for the cross-posting, but I haven't had a clear answer (or any answer) to this in nearly a week of asking, and I see at least one other person cross compiling a driver they've written seems to having the same issue, so I want to try to get some answers. I have written a driver - snd-aica for sound on a Sega Dreamcast. This is a legacy device, not PCI or anything like that, so it's a Platform device. It works very well with the oss emulation, so I assume it correctly handles PCM. But I get this: $ aplay -l List of PLAYBACK Hardware Devices card 0: AICA [AICA], device 0: AICA PCM [AICA PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ aplay -L null Discard all samples (playback) or generate zero samples (capture) and as a result nothing plays: $ aplay -d:hw0,0 /aine-email.wav Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ALSA lib pcm_plug.c:773:(snd_pcm_plug_hw_refine_schange) Unable to find an usable access for '(null)' aplay: set_params:895: Access type not available all the relevant files for an ordinary alsa install are about: $ pwd /usr/share/alsa $ ls -l -rw-r--r--1 default default 8611 Jan 3 23:45 alsa.conf drwxr-xr-x3 default default 4096 Jan 3 23:45 cards drwxr-xr-x2 default default 4096 Jan 3 23:45 pcm -rw-r--r--1 default default 132 Jan 3 23:45 smixer.conf -rw-r--r--1 default default 3205 Jan 3 23:45 sndo-mixer.alisp drwxr-xr-x2 default default 4096 Jan 2 20:26 speaker-test But there are no configuration files for this device. And alsaconf does not detect it - but then it's not PnP so that is no surprise. In common with a typical embedded device the Dreamcast has a not very sophisticated setup - built using an nfs-root mount and busybox/buildroot. What configuration files am I required to have to get alsa to work? It's a fairly simple question I would have thought... how do I create them and where do I put them? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On Jan 5, 2008 4:37 PM, Adrian McMenamin [EMAIL PROTECTED] wrote: Apologies for the cross-posting, but I haven't had a clear answer (or any answer) to this in nearly a week of asking, and I see at least one other person cross compiling a driver they've written seems to having the same issue, so I want to try to get some answers. The missing config file is NOT THE PROBLEM. The problem is almost certainly that your cross compile was not correct and it's looking for the DEVICE INDEPENDENT config files in the wrong place. I posted a solution to alsa-devel over a year ago. If you can't find it you need to look harder. Search for something like alsa-devel cross compile problems. You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Lee - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? Please file a bug - otherwise ALSA programmers will continue writing code which does not print full paths to files it tries to open. Thanks, Sergei. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
Sergei Steshenko wrote: On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? Please file a bug - otherwise ALSA programmers will continue writing code which does not print full paths to files it tries to open. Thanks, Sergei. What is the problem? Just use: strace aplay -L 21 |grep open That will list all files being opened. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On Sun, 06 Jan 2008 00:24:11 + James Courtier-Dutton [EMAIL PROTECTED] wrote: Sergei Steshenko wrote: On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? Please file a bug - otherwise ALSA programmers will continue writing code which does not print full paths to files it tries to open. Thanks, Sergei. What is the problem? Just use: strace aplay -L 21 |grep open That will list all files being opened. The problem is the word all - I wanna see just the failing ones. And, IIRC, earlier in this or similar thread was stated that 'strace' wasn't working for ARM plarform. ... My background is VLSI. I'm just wondering about the fate of big vendors like SYNOPSYS or Cadence telling their customers: What's the problem ? Just run our simulation or synthesis or layout tool with 'strace'. Its not that the above vendors; software is bugless, but WRT printing file names they definitely show respect for their customers. Regards, Sergei. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On 06/01/2008, James Courtier-Dutton [EMAIL PROTECTED] wrote: Sergei Steshenko wrote: On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: What is the problem? Just use: strace aplay -L 21 |grep open That will list all files being opened. Because there is no version strace that will build for this platform afaics - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
On 05/01/2008, Sergei Steshenko [EMAIL PROTECTED] wrote: On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? Please file a bug - otherwise ALSA programmers will continue writing code which does not print full paths to files it tries to open. I am not going to file a bug until I'm clear what is wrong. Can someone not tell me what files to patch to find out? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Getting a driver to support alsa natively
Adrian McMenamin wrote: On 05/01/2008, Sergei Steshenko [EMAIL PROTECTED] wrote: On Sat, 5 Jan 2008 22:13:59 + Adrian McMenamin [EMAIL PROTECTED] wrote: On 05/01/2008, Lee Revell [EMAIL PROTECTED] wrote: You also need to find some way to confirm or deny that alsa-lib is trying to open the right files. Given this is nfs-root, the only realistic way is to hack the sources and find out what the path is. I am happy to do that, especially if someone indicates which function/file I should start with? Please file a bug - otherwise ALSA programmers will continue writing code which does not print full paths to files it tries to open. I am not going to file a bug until I'm clear what is wrong. Can someone not tell me what files to patch to find out? ./alsa-lib/src/conf.c This defines where it looks for the config files. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
