From: Timur Tabi <timur@freescale.com>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: Possible problem with snd_pcm_oss_sync()
Date: Tue, 20 May 2008 11:03:42 -0500 [thread overview]
Message-ID: <4832F65E.5070008@freescale.com> (raw)
-------- Original Message --------
Subject: RE: Regarding MPC8610 BSP question and issue
Date: Tue, 20 May 2008 08:55:46 -0700
From: Hayasaka Manabu <manabu.hayasaka@freescale.com>
To: Hayasaka Manabu <manabu.hayasaka@freescale.com>, Johnson Kelly
<Kelly.Johnson@freescale.com>
CC: sun york <yorksun@freescale.com>, Namiki Ayumi
<namiki@freescale.com>, Beck Glenn <Glenn.Beck@freescale.com>, Cox Kevin
<K.Cox@freescale.com>, Hamano Masahiro <M.Hamano@freescale.com>, Tabi
Timur <timur@freescale.com>
References:
<E03EE6E38549E949AE8138F60493E1E801C49A0C@zja67exm20.fsl.freescale.net>
<4807899D.3000901@freescale.com>
<E03EE6E38549E949AE8138F60493E1E801DA1B11@zja67exm20.fsl.freescale.net>
<48110FCF.7070302@freescale.com>
<BD243C8D8F65694A966948E9D51F9815C29409@zja67exm21.fsl.freescale.net>
<48189540.9060309@freescale.com>
<BD243C8D8F65694A966948E9D51F9815C29422@zja67exm21.fsl.freescale.net>
<E03EE6E38549E949AE8138F60493E1E801DA25D9@zja67exm20.fsl.freescale.net>
<4821CA02.2020504@freescale.com>
<E03EE6E38549E949AE8138F60493E1E801FA11C8@zja67exm20.fsl.freescale.net>
<4829C444.7010206@freescale.com>
<E03EE6E38549E949AE8138F60493E1E801FA13D2@zja67exm20.fsl.freescale.net>
<482B1D10.7090402@freescale.com> <482B2699.8020409@freescale.com>
I'm working with a customer that has discovered a possible problem with OSS
emulation. Unfortunately, I don't have a lot of experience with OSS, so I need
help understanding whether the customer's observations point to a real problem
or not.
The customer is using an old application called "bplay" to test OSS audio
support on our hardware. The application works fine on x86, but fails on our
PowerPC board. It could be an endian issue, but I doubt it.
Here is the forwarded email (slightly edited). Can someone familiar with the
OSS "sync" functionality comment?
---------------
They reported that it seemed some ioctl commands in the OSS emulation did not
work correctly.
The tested procedure of the ioctl commands are as following,
#1) Stopped audio stream output after doing followings:
1. Opening /dev/mixer
2. Getting a channel value (0x00000001) that is used for "ioctl(fd,
SOUND_MIXER_READ_DEVMASK, &Sndsts);".
3. Write audio volume information by "ioctl(fd,
SOUND_MIXER_WRITE_VOLUME, &Value);",
#2) Stopped audio stream output after doing following:
1. Opening /dev/dsp
2. Executing command "ioctl(fd, SNDCTL_DSP_SYNC, NULL);",
XXXX found that by commenting out the "sync_audio" function on the source
code of "bplay" made "bplay" work. So XXXX suspects the implementation of the
ioctl on the OSS emulation may have a problem.
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2008-05-20 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 16:03 Timur Tabi [this message]
2008-05-20 18:57 ` Possible problem with snd_pcm_oss_sync() Timur Tabi
2008-05-21 11:25 ` Clemens Ladisch
2008-05-21 10:44 ` Takashi Iwai
2008-05-21 14:15 ` Timur Tabi
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=4832F65E.5070008@freescale.com \
--to=timur@freescale.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.