From: BenH <bh40@calva.net>
To: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] little-endian dmasound silently fails
Date: Sat, 5 Feb 2000 14:26:13 +0100 [thread overview]
Message-ID: <20000205142613.026592@192.168.1.10> (raw)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.1000204221814.20504A-100000@ofey.inetnebr.com>
On Fri, Feb 4, 2000, Takashi Oe <toe@unlserve.unl.edu> wrote:
>Maybe because it does support it? Well, seriously, I've just checked the
>driver is okay wrt *S16_LE/BE at least on AWACS rev. 2.
>
>First, I wrote an app to play a sound file correctly when AFMT_S16_BE is
>specified. Then, I modified the app so that it will byte swap the 16-bit
>data but still with AFMT_S16_BE. As expected, it made some annoying
>noise when it was asked to play the same sound file. Now, I modified the
>code again to let it specify AFMT_S16_LE instead. Well, it played the
>sound file correctly just as hoped.
>
>I know a lot of people are not happy about our sound driver, but I
>don't think this is dmasound's fault. Luckily for us, many "broken"
>OSS-compatible apps tend to work just fine if we simply modify them to ask
>for AFMT_S16_NE not *_LE, though performance critical apps should be fixed
>with more effort.
Actually, I had some reports about this problem too and I'm wondering if
all revisions of AWACS actually support byte swapping. (I think I
remember seeing a comment on this list telling explicitely that some
revisions didn't support it).
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-05 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 23:20 [patch] little-endian dmasound silently fails Brad Midgley
2000-02-04 23:59 ` Takashi Oe
2000-02-05 3:55 ` Brad Midgley
2000-02-05 5:56 ` Takashi Oe
2000-02-05 13:26 ` BenH [this message]
2000-02-06 4:50 ` Takashi Oe
2000-02-06 13:34 ` BenH
2000-02-06 11:55 ` Brad Boyer
2000-02-06 10:22 ` Brad Midgley
2000-02-06 8:15 ` Takashi Oe
2000-02-05 19:12 ` Giuliano Pochini
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=20000205142613.026592@192.168.1.10 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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;
as well as URLs for NNTP newsgroup(s).