From: Takashi Oe <toe@unlserve.unl.edu>
To: Iain Sandoe <iain@sandoe.co.uk>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap
Date: Thu, 18 Jan 2001 18:51:11 -0600 [thread overview]
Message-ID: <B68CEB9E.5812%toe@unlserve.unl.edu> (raw)
In-Reply-To: <20010119000317.336152EFC5@apollo.valhalla.net>
On 1/18/01 6:04 PM, Iain Sandoe wrote:
>
> I forgot to say...
>
> 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.
Takashi Oe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 0:04 [PATCH] 2.4.1p4 : dmasound ed21- Pismo byte-swap Iain Sandoe
2001-01-19 0:51 ` Takashi Oe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-19 1:47 Iain Sandoe
2001-01-19 2:03 ` Takashi Oe
2001-01-19 2:30 Iain Sandoe
2001-01-19 3:05 ` Takashi Oe
2001-01-19 4:11 Iain Sandoe
2001-01-19 5:21 ` Takashi Oe
2001-01-19 10:04 Iain Sandoe
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=B68CEB9E.5812%toe@unlserve.unl.edu \
--to=toe@unlserve.unl.edu \
--cc=iain@sandoe.co.uk \
--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).