From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] to swap or not to swap
Date: Tue, 13 Nov 2001 11:42:48 -0800 [thread overview]
Message-ID: <20011113114247.G3053@tausq.org> (raw)
In-Reply-To: <20011113142545.E11817@parcelfarce.linux.theplanet.co.uk>
> depends on the PCI bridge and MMU whether you need to do bytesexswapping
> in software or not. see section 9 in the Dino ERS, page 61 for how PA
> does this.
Empirically I've found this not to be the case. For example, if i need
to write 0x01 to byte 0 of a 16-bit PCI register, I've found I need to
do:
writew(0x0100, addr) on parisc
vs
writew(0x0001, addr) on x86
Grant also seems to be of the opinion that cpu data needs to be swapped
before written to PCI devices... so does that mean that if i wrote
something like:
writew(cpu_to_le16(foo), addr)
then on things like parisc it gets swapped once, and on things like
sparc it gets swapped twice?
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2001-11-13 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 8:30 [parisc-linux] to swap or not to swap Randolph Chung
2001-11-13 14:25 ` Matthew Wilcox
2001-11-13 19:42 ` Randolph Chung [this message]
2001-11-13 20:32 ` Grant Grundler
2001-11-13 22:51 ` Alan Cox
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=20011113114247.G3053@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@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