From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap
Date: Fri, 19 Jan 2001 01:47:39 +0000 [thread overview]
Message-ID: <20010119014611.67C3F2F00B@apollo.valhalla.net> (raw)
>> this should (now I fixed a typo in the machine name) also solve the LE
>> byte-swapping problem on Pismo (by soft-swapping).
>
> Can't apps cope with it if it doesn't do the byte-swapping in H/W? If it
> can, I think the code should be removed. No software translation in kernel
> if we can avoid it at all.
I agree 100% - the kernel should _never_ have been doing this stuff in the
first place (it can't even make a particularly good job of some of it
without fp).... and, AFAIK, that is the way of things for ALSA.
However, in OSS-land, it seems that quite a few apps rely on it (or don't
treat endian-ness sensibly) - OK, so they are, in some sense, buggy ...
... by comparison with the large amount of other code already in there to do
rate expansion and compression/decompression it is a relatively small price
to pay for having all pmac machines behave the same...
... at the next revision of the driver we could try issuing it with "16bit
44k1 Signed BE" only - and see how much of the desktop world works ;-)
iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-19 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 1:47 Iain Sandoe [this message]
2001-01-19 2:03 ` [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap Takashi Oe
-- strict thread matches above, loose matches on Subject: below --
2001-01-19 10:04 Iain Sandoe
2001-01-19 4:11 Iain Sandoe
2001-01-19 5:21 ` Takashi Oe
2001-01-19 2:30 Iain Sandoe
2001-01-19 3:05 ` Takashi Oe
2001-01-19 0:04 Iain Sandoe
2001-01-19 0:51 ` Takashi Oe
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=20010119014611.67C3F2F00B@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--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).