Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] alsa lib problem
Date: Mon, 26 Jan 2009 19:12:20 +0000	[thread overview]
Message-ID: <497E0B14.8040801@carallon.com> (raw)

Hi All,

I have alsa-lib compiling for my arm target however aplay fails to work with the kernel 
reporting:

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 it appears that 
when compiling alsa-lib it thought it was 8 bytes. I assume this is because something in 
the toolchain on the host PC or the alsa-lib build is wrong and it is picking up a define 
from outside buildroot.

Does this sound possible? How do I establish which definition it is using?

Thanks,

Will.
-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

             reply	other threads:[~2009-01-26 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 19:12 Will Wagner [this message]
2009-01-27  5:49 ` [Buildroot] alsa lib problem Peter Korsgaard
2009-01-27 12:32   ` Will Wagner
2009-01-27 12:44     ` Hans-Christian Egtvedt
2009-01-27 12:47       ` Will Wagner
2009-01-27 12:56         ` Peter Korsgaard
2009-01-27 12:45     ` Peter Korsgaard
2009-01-28 15:34     ` Peter Korsgaard

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=497E0B14.8040801@carallon.com \
    --to=will_wagner@carallon.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox