From: Benjamin Herrenschmidt <bh40@calva.net>
To: Elliot Lee <sopwith@redhat.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: esound for PPC
Date: Tue, 5 Oct 1999 10:54:31 +0200 [thread overview]
Message-ID: <19991005105431.012853@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9910041156210.15818-100000@lacrosse.corp.redhat.com>
On Mon, Oct 4, 1999, Elliot Lee <sopwith@redhat.com> wrote:
>That isn't the problem here. Apparently someone put a bad hack into the
>PPC sound driver that makes it default to little endian instead of big
>endian format, and esound is expecting that "native endian" on the sound
>device is "big endian", not "little endian".
I may be wrong, but to me, this looks like a bug in esound. The driver
seems capable of telling the application about it's current format and
can be told to change it. If esound does assumptions about the default
format instead of querying the driver, then esound is broken. (Also the
driver may have been switched to another format by an application before
esound takes control anyway. I don't remember which of /dev/audio or
/dev/dsp will keep the current setting so this may not be an issue).
I agree that the driver lacks a call to query about the native endian, so
if you really want to, you can add code to esound to force-switch to big
endian on PowerMac, but at least, it should be fixed to not rely on a
supposed default setting.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@mipsys.com>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-05 8:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 3:48 esound for PPC Eric Dorland
1999-10-03 4:03 ` Elliot Lee
1999-10-03 18:54 ` Eric Dorland
1999-10-03 19:23 ` Tom Rini
1999-10-03 21:46 ` Elliot Lee
1999-10-04 6:27 ` Geert Uytterhoeven
1999-10-04 15:58 ` Elliot Lee
1999-10-05 8:54 ` Benjamin Herrenschmidt [this message]
1999-10-05 11:36 ` Elliot Lee
1999-10-06 0:40 ` Eric Dorland
1999-10-11 6:06 ` Eric Dorland
1999-10-11 19:43 ` Eric Dorland
1999-10-11 20:09 ` Tom Rini
1999-10-12 3:03 ` Ryan Nielsen
1999-10-12 3:10 ` Tom Rini
[not found] ` <19991014193940.A1143@HSE-MTL-ppp4505.qc.sympatico.ca>
[not found] ` <19991017190502.A13068@gondolin.asf>
[not found] ` <19991023152110.A525@HSE-MTL-ppp4445.qc.sympatico.ca>
[not found] ` <19991023203334.A26715@gondolin.asf>
[not found] ` <19991024223141.A758@HSE-MTL-ppp4328.qc.sympatico.ca>
1999-10-26 5:29 ` Ryan Nielsen
1999-10-26 6:30 ` recv programming problem Morningstar
1999-10-26 14:10 ` esound for PPC Dan Malek
1999-10-12 3:10 ` Eric Dorland
1999-10-12 3:20 ` Tom Rini
1999-10-12 4:26 ` Eric Dorland
1999-11-02 18:01 ` Elliot Lee
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=19991005105431.012853@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sopwith@redhat.com \
/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).