From: Michel Lanners <mlan@cpu.lu>
To: geert@linux-m68k.org
Cc: dwp@bluesteelnet.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Update: RE: G4 + Linux + PCI device + x86 driver = 0
Date: Mon, 6 Dec 1999 07:51:56 +0100 (CET) [thread overview]
Message-ID: <199912060651.HAA00385@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.LNX.4.05.9912052040150.376-100000@callisto.of.borg>
Hi Geert,
On 5 Dec, this message from Geert Uytterhoeven echoed through cyberspace:
>> David pointed out le16_to_cpu() et al; personally, I use in_/out_le32
>> et al for access to PCI memory space like this:
>>
>> out_le32 (&device->register, val);
>
> Which is wrong! Portable PCI memory space accesses must be done using
> {read,write}[bwl]()!
Ooopppss.... Thanks for letting me know. I guess it doesn't make much
difference, because the code I use it in is purely PowerMac, but
anyway... I'll go read...
> See linux/Documentation/IO-mapping.txt
....that ;-)
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-12-06 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-14 0:55 G4 + Linux + PCI device + x86 driver = 0 David W. Patmore
1999-11-14 11:41 ` Takashi Oe
1999-11-14 23:50 ` Paul Mackerras
1999-11-15 9:33 ` Adrian Cox
1999-12-03 23:00 ` Update: " David W. Patmore
1999-12-04 0:50 ` David Edelsohn
1999-12-04 1:13 ` endian-swapping Hollis R Blanchard
1999-12-04 1:56 ` endian-swapping David Edelsohn
1999-12-04 19:13 ` endian-swapping Gabriel Paubert
1999-12-04 11:57 ` Update: RE: G4 + Linux + PCI device + x86 driver = 0 Michel Lanners
1999-12-05 19:42 ` Geert Uytterhoeven
1999-12-06 6:51 ` Michel Lanners [this message]
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=199912060651.HAA00385@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=dwp@bluesteelnet.com \
--cc=geert@linux-m68k.org \
--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).