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 > >> > a

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

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 > SN

Re: [Alsa-user] Getting a driver to support alsa natively

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 tha

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 > >

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:

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

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

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 c

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 n

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 t

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 2>&1 |grep open > > That will list all files being opened. > Becau

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. >>> >>>

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 realist

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

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 iss

[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-aic