From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isa_read/write not available on ppc - solution suggestions ??
Date: Tue, 1 May 2001 20:45:43 +0100 [thread overview]
Message-ID: <20010501204543.B3541@flint.arm.linux.org.uk> (raw)
In-Reply-To: <OF7A9C6B22.E1638E60-ON85256A3F.004EADC7@urscorp.com> <9cmrcv$20e$1@penguin.transmeta.com>
In-Reply-To: <9cmrcv$20e$1@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, May 01, 2001 at 10:22:39AM -0700
On Tue, May 01, 2001 at 10:22:39AM -0700, Linus Torvalds wrote:
> I bet that the patch will be smaller too. It's a simple case of
> - do the ioremap() _once_ at bootup, save the result in a static
> variable somewhere.
> - implement the (one-liner) isa_readx/isa_writex functions.
>
> On many architectures you don't even need to do the ioremap, as it's
> always available (same as on x86).
Talking around this issue, is there any chance of getting the
official use of the first parameter to ioremap documented in
Documentation/IO-mapping.txt please? There appears to be
confusion as to whether it is:
a) PCI bus address
b) CPU untranslated address
Currently, IO-mapping.txt seems to imply (a), but I believe that
a lot of people on lkml will disagree with that.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-05-01 19:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 15:27 isa_read/write not available on ppc - solution suggestions ?? mike_phillips
2001-05-01 17:22 ` Linus Torvalds
2001-05-01 19:45 ` Russell King [this message]
2001-05-01 21:19 ` Linus Torvalds
2001-05-01 21:31 ` Russell King
2001-05-01 22:46 ` Linus Torvalds
2001-05-02 15:10 ` Jonathan Lundell
2001-05-02 1:02 ` Paul Mackerras
2001-05-02 19:28 ` Benjamin Herrenschmidt
2001-05-02 7:26 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 13:12 mike_phillips
2001-05-03 11:08 ` Anton Blanchard
2001-05-01 17:41 mike_phillips
2001-05-01 13:52 mike_phillips
2001-05-01 4:32 ` Arnaldo Carvalho de Melo
2001-05-01 14:35 ` Alan Cox
2001-05-01 14:50 ` Brian Gerst
2001-05-01 15:14 ` Alan Cox
2001-05-01 14:36 ` Brian Gerst
2001-05-01 17:33 ` Geert Uytterhoeven
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=20010501204543.B3541@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.