From: Benjamin Herrenschmidt <bh40@calva.net>
To: Patrick Lerda <Lerda@microprocess.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: insw/outsw/insl/outsl (was: Re: your mail)
Date: Fri, 18 Feb 2000 14:48:57 +0100 [thread overview]
Message-ID: <20000218144857.016035@mailhost.mipsys.com> (raw)
In-Reply-To: <B0CAE42C9EE0D311AAAD00500422FC6302CD74@iis000.microdata.fr>
On Fri, Feb 18, 2000, Patrick Lerda <Lerda@microprocess.com> wrote:
>In my opinion we need new functions for quick byte copy, with new names.
>The names insw/outsw/insl/outsl are to close to inw, outw, insw...;
>these functions work with the PCI bus, and data need a conversion to
>little-endian,
>before read and write operation.
>
>We need new functions and fix the kernel.
I'm not sure we need new functions at all.
Do you know a single case where swapping would actually be required with
insw/outsw/insl/outsl ?
All cases I encountered so far (IDE, sound, ethernet), those are used to
transfer stream of bytes between device and memory. In this case, the
access width is irrelevant and no swapping must be done.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-02-18 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B0CAE42C9EE0D311AAAD00500422FC6302CD74@iis000.microdata.fr>
2000-02-18 13:48 ` Benjamin Herrenschmidt [this message]
[not found] <00021714275405.25243@argo.linuxcare.com.au>
2000-02-18 12:17 ` insw/outsw/insl/outsl (was: Re: your mail) Geert Uytterhoeven
2000-02-18 13:45 ` Gabriel Paubert
2000-02-18 13:52 ` Momchil Velikov
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=20000218144857.016035@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=Lerda@microprocess.com \
--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).