From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Derrik Pates <demon@devrandom.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Fix for PPC audio devices that can't reendianize samples
Date: Fri, 10 Aug 2001 19:28:34 +0100 [thread overview]
Message-ID: <20010810183346.9F02E2F040@apollo.valhalla.net> (raw)
> The attached patch adds code to drivers/sound/dmasound/trans_16.c to
> byteswap little-endian audio samples for hardware that needs it (like the
> DACA audio chip in the iBook and iBook FireWire), and also marks the DACA
> in the iBook FireWire as being unable to handle little-endian audio
> samples (in dmasound_awacs.c).
we've been round this loop ;-)))
the reason that the byte-swap code was taken out of trans_16.c is that it
will never be allowed into the kernel.
The way to solve the problem is to:
(a) as you've done, mark the DACA and so on as BE-only (which, I thought was
already done in the latest patches - barring the Keylargo rev.3 detection).
(b) if applications don't work properly with BE-only devs then bang on the
app maintainer (or send patches) to fix it.
Otherise you end up with having to maintain a never-to-be-merged patch
against dmasound (and believe me, that's a PITA).
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-10 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 18:28 Iain Sandoe [this message]
2001-08-11 17:46 ` Fix for PPC audio devices that can't reendianize samples Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 14:28 Iain Sandoe
2001-08-12 10:59 Iain Sandoe
2001-08-11 23:21 Iain Sandoe
2001-08-12 8:47 ` Geert Uytterhoeven
2001-08-13 14:08 ` Derrik Pates
2001-08-13 14:58 ` Geert Uytterhoeven
2001-08-10 15:45 Derrik Pates
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=20010810183346.9F02E2F040@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=demon@devrandom.net \
--cc=linuxppc-dev@lists.linuxppc.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 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).