From: Randolph Chung <randolph@tausq.org>
To: Daniel Engstrom <5116@telia.com>
Cc: Jochen Friedrich <jochen@scram.de>,
linux-tr@linuxtr.net,
HP900 PARISC mailing list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] IBM TR patch
Date: Tue, 15 Jan 2002 17:23:43 -0800 [thread overview]
Message-ID: <20020116012343.GV3247@tausq.org> (raw)
In-Reply-To: <20020115231052.A4018@zaphod.halden.lillfab.se>
> I think the driver was correct. The i/o layer should not try to byteswap
> the io requests, because it can not second-guess what the driver is doing.
For reference, you may wish to read
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-November/014606.html
Originally the parisc {read,write}[wl] macros did not swap, but this
breaks many PCI drivers. For example, we used to have hppa specific code in the
sym53c8xx driver that did the swapping....
> And in the case of the tr driver it now does two swaps for each word it tranfers on
> big endian platforms instad of zero.
I agree this is not optimal, altho, as Alan Cox pointed out in
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-November/014527.html
double swaps may be optimized out by the compiler.
>
> The ne2000 driver had the same problem, but I removed the swaps from the parisc i/o code
> instad of touching the driver.
for parisc we follow the ppc convention of defining __raw_{read,write}[wl]
that are host-endian. perhaps the drivers can use this instead?
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2002-01-16 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 19:53 [parisc-linux] IBM TR patch Jochen Friedrich
2002-01-15 18:11 ` Randolph Chung
2002-01-15 18:18 ` Matthew Wilcox
2002-01-15 19:12 ` Jochen Friedrich
2002-01-15 19:07 ` Jochen Friedrich
2002-01-15 22:10 ` Daniel Engstrom
2002-01-16 1:23 ` Randolph Chung [this message]
2002-01-16 20:20 ` Jochen Friedrich
2002-01-19 12:20 ` Daniel Engstrom
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=20020116012343.GV3247@tausq.org \
--to=randolph@tausq.org \
--cc=5116@telia.com \
--cc=jochen@scram.de \
--cc=linux-tr@linuxtr.net \
--cc=parisc-linux@lists.parisc-linux.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