Hi, Clemens:

Sorry for my mistake. After avoiding using mmap to transer data from userface to kernel, alsa will use snd_pcm_ioctl_compat to do this work. I check the returned value, and it seems good. but error still happned.

[ 198.838437] 837 (aplay) snd_pcm_ioctl_sync_ptr_compat++

[ 198.845630] 837 (aplay) state:0x2

[ 198.850803] 837 (aplay) hw_ptr:0x0

[ 198.855658] 837 (aplay) tstamp:0x0

[ 198.860934] 837 (aplay) suspend_stat:0x0

[ 198.866878] 837 (aplay) tstamp:0x0

[ 198.871682] 837 (aplay) appl_ptr:0x0

[ 198.877199] 837 (aplay) avail_min:0x300

[ 198.882574] 837 (aplay) snd_pcm_ioctl_sync_ptr_compat--

[ 198.890779] 837 (aplay) ======snd_pcm_ioctl_compat++++++++

[ 198.898759] 837 (aplay) ======snd_pcm_ioctl_compat11

[ 198.905507] 837 (aplay) ========snd_pcm_ioctl_xferi_compat++++

[ 198.960915] 837 (aplay) ========snd_pcm_ioctl_xferi_compat-----, result=0x300, buf=0x33b640, frames=0x300

[ 198.982513] 837 (aplay) Bad mode in Error handler detected, code 0xbf000000

[ 198.992198] 837 (aplay) CPU: 0 PID: 837 Comm: aplay Tainted: G D 3.10.0+ #44

[ 199.002870] 837 (aplay) task: ffffffc019adb0c0 ti: ffffffc019a36000 task.ti: ffffffc019a36000

[ 199.014226] 837 (aplay) PC is at 0xf7228aec

[ 199.020120] 837 (aplay) LR is at 0x0

[ 199.025312] 837 (aplay) pc : [<00000000f7228aec>] lr : [<0000000000000000>] pstate: 60000010

[ 199.036415] 837 (aplay) sp : ffffffc019a37ff0

BR Cosmo

2013/11/21 Clemens Ladisch clemens@ladisch.de

Please don't top-post.

Cosmo wrote:

...

Hi, Clemens

Don't drop the mailing list from replies.

...

Do you mean we need to change ALSA's mmap code to adapt to ARM64.

Maybe.

...

Do you know how to port it?

No.

Regards, Clemens