From: Will Wagner <will_wagner@carallon.com>
To: alsa-devel@alsa-project.org
Subject: alsa-lib failing at runtime
Date: Wed, 28 Jan 2009 13:43:51 +0000 [thread overview]
Message-ID: <49806117.8090205@carallon.com> (raw)
Hi All,
I have found a problem with alsa-lib 1.0.19 running on an embedded arm board. It all
compiles ok but aplay fails to play a .wav file and the kernel reports this error:
ALSA sound/core/pcm_native.c:2587: unknown ioctl = 0x80184132
Decoding this ioctl it is SNDRV_PCM_IOCTL_CHANNEL_INFO defined in asound.h.
The reason it is not working is that the kernel and alsa-lib think that the
sndrv_pcm_channel_info struct is different sizes.
The definition in asound.h is:
struct sndrv_pcm_channel_info {
unsigned int channel;
off_t offset; /* mmap offset */
unsigned int first; /* offset to first sample in bits */
unsigned int step; /* samples distance in bits */
};
The problem is that when compiling linux it thinks off_t is 4 bytes but when compiling
alsa-lib it thought it was 8 bytes.
After discussion on the buildroot mailing list (see
http://lists.busybox.net/pipermail/buildroot/2009-January/025458.html) it seems like for
the kernel off_t is always 4 bytes but for user space it can be either 4 or 8 bytes
depending on whether large file support is enabled.
It appears that the fix is that the type of offset should be changed to long.
Hope this all makes sense.
Thanks,
Will.
--
------------------------------------------------------------------------
Will Wagner will_wagner@carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2009-01-28 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 13:43 Will Wagner [this message]
2009-01-28 14:03 ` alsa-lib failing at runtime Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49806117.8090205@carallon.com \
--to=will_wagner@carallon.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.