From: David Blythe <blythe@routefree•com>
To: Ralph Blach <rblach@intrex•net>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: es1371.o sound module on a IBM405 gp walnut
Date: Sun, 18 Mar 2001 20:58:06 -0800 [thread overview]
Message-ID: <3AB591DD.6ABFCF1B@routefree.com> (raw)
In-Reply-To: 3AB4E320.233162CD@intrex.net
Ralph Blach wrote:
>
> I am trying to get an es1371. sound module working on an IBM405 walunt
> developement kit. 8 bit sound works ok
> but 16 bit sound sounds like noise. Will this driver have to be made
> Endian aware?
Yes and no. A lot of the player programs are not very endian savy.
Typically what I have seen happen on bigendian ppc is that either the
player asks for AFMT_S16_LE but really sends AFMT_S16_BE samples and
you get noise (sox/play does this but I worked on a patch for this with
Chris Bagwell so hopefully it is available now) or it asks for
AFMT_S16_BE samples and the driver doesn't support this and the request
format ioctl defaults to AFMT_U8 instead and the player ends up sending
8 bit samples instead of 16, because it didn't also do a query for
AFMT_S16_LE. An earlier version of madplay was doing this (I tooked the
easy way out and had our sound driver return AFMT_S16_LE as the default
format to get around this, but the query algorithm in madplay could be
made better). It looks like the es1371 driver defaults to AFMT_U8.
david
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-19 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-18 16:32 es1371.o sound module on a IBM405 gp walnut Ralph Blach
2001-03-19 0:02 ` Brad Parker
2001-03-19 4:58 ` David Blythe [this message]
[not found] <200103191113.GAA58475@p2.parker.boston.ma.us>
2001-03-20 1:01 ` Ralph Blach
2001-03-20 1:08 ` David Blythe
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=3AB591DD.6ABFCF1B@routefree.com \
--to=blythe@routefree$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=rblach@intrex$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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