From: Brad Boyer <flar@pants.nu>
To: bh40@calva.net (BenH)
Cc: toe@unlserve.unl.edu (Takashi Oe), linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] little-endian dmasound silently fails
Date: Sun, 6 Feb 2000 03:55:42 -0800 (PST) [thread overview]
Message-ID: <200002061155.GAA06862@marcus.pants.nu> (raw)
In-Reply-To: <20000205142613.026592@192.168.1.10> from "BenH" at Feb 05, 2000 02:26:13 PM
BenH wrote:
> 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).
Well, I know I complained several times, but I found out recently when I
did some more careful testing that I was wrong. I have a rev 2 AWACS chip
in my computer, and the byteswap does work. My problem was that I had a
number of programs which set the format improperly, and I didn't notice
the problem when I looked at the code. As an example, snes9x explicitly
asks for a little-endian format, then generates the sound in native
order. Unless you can find someone with a rev 1 AWACS chip and test
that one, I imagine you can assume that all of them support byteswap
properly. And since the 7600 I have is one of the oldest machines that
is supported, I imagine you won't find anyone with rev 1 unless they
changed in between the 7500 and 7600. I would guess that rev 1 was
used in the nubus powermacs.
Brad Boyer
flar@pants.nu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-06 11:55 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
2000-02-06 4:50 ` Takashi Oe
2000-02-06 13:34 ` BenH
2000-02-06 11:55 ` Brad Boyer [this message]
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=200002061155.GAA06862@marcus.pants.nu \
--to=flar@pants.nu \
--cc=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).