All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problems with 32 bit apps on 64 bit OS using dmix and snd-ioctl32
Date: Thu, 06 Sep 2007 11:26:35 +0100	[thread overview]
Message-ID: <46DFD5DB.6030204@moving-picture.com> (raw)
In-Reply-To: <s5hbqch6nrf.wl%tiwai@suse.de>

Takashi Iwai wrote:

> Hm, maybe it's better to specify 2.6.16 or so for SND_SOC in
> alsa-driver/kconfig-vers.  Could you check whether it works?

Yes, this works - after I figured out that I needed to regenerate the 
configure script after changing kconfig-vers ...

alsa-driver 1.0.15rc1 now builds OK on RHEL4/CentOS4 (with a patched 
misc/ac97_bus.c and SND_SOC set to 2.6.16 in kconfig-vers)

>>However, with these 1.0.15rc1 modules installed, and using 
>>alsa-lib-1.0.15rc1, I get exactly the same problem with 32 bit apps:
>>
>>Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
>>aplay: pcm_write:1268: write error: Invalid argument
>>
>>amd dmesg has:
>>
>>ioctl32(aplay:6228): Unknown cmd fd(3) cmd(40045402){00} arg(ffffac98) 
>>on /dev/snd/timer
>>ioctl32(aplay:6228): Unknown cmd fd(5) cmd(c008551a){00} arg(0806ccd0) 
>>on /dev/snd/controlC0
>>ioctl32(aplay:6228): Unknown cmd fd(5) cmd(c008551b){00} arg(0806ccd0) 
>>on /dev/snd/controlC0
>>ioctl32(aplay:6228): Unknown cmd fd(3) cmd(000054a0){00} arg(00000325) 
>>on /dev/snd/timer
> 
> 
> Do you use the latest alsa-lib, too?
> The old alsa-lib tries only the old ioctl, of course...

Yes, I've installed the 32 bit and 64 bit alsa-lib-1.0.15rc1 packages - 
and I still get the above errors ...

Do I need to build alsa-lib with any special options? I configured 
alsa-lib using:

  configure --enable-static=yes --datadir=/etc

As this is how the 1.0.6 alsa-lib RHEL4 RPM was configured.

Does building alsa-lib depend on the alsa-driver version installed? - as 
I built the 32 bit version on a 'stock' CentOS4/RHEL4 install that 
didn't have the alsa-driver 1.0.15rc1 installed - would this make a 
difference?

Thanks

James Pearson

  reply	other threads:[~2007-09-06 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 11:10 Problems with 32 bit apps on 64 bit OS using dmix and snd-ioctl32 James Pearson
2007-09-05 12:51 ` Takashi Iwai
2007-09-05 14:38   ` James Pearson
2007-09-05 15:23     ` Takashi Iwai
2007-09-05 15:36       ` James Pearson
2007-09-05 16:11         ` Takashi Iwai
2007-09-05 16:54           ` James Pearson
2007-09-05 17:11             ` Takashi Iwai
2007-09-06 10:26               ` James Pearson [this message]
2007-09-06 10:51                 ` Takashi Iwai
2007-09-06 11:56                   ` James Pearson
2007-09-06 12:08                     ` Takashi Iwai
2007-09-06 12:15                       ` James Pearson
2007-09-06 13:06                         ` Takashi Iwai
2007-09-11 21:56             ` James Pearson

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=46DFD5DB.6030204@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.