From: mike_phillips@urscorp.com
To: linux-kernel@vger.kernel.org
Subject: Re: isa_read/write not available on ppc - solution suggestions ??
Date: Tue, 1 May 2001 13:41:53 -0400 [thread overview]
Message-ID: <OF8F30DD01.CDAFFB0E-ON85256A3F.005BE8E3@urscorp.com> (raw)
> I would suggest the opposite approach instead: make the PPC just
> support isa_readx/isa_writex instead.
>
> Much simpler, and doesn't need changes to (correct) driver sources.
>
> 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).
That would be my preferred solution as well. The one-liners are easy, the
ioremap may be more fun. Time to investigate the ppc code and docs.
Unless one of the kindly ppc maintainers who knows far more about the arch
than me would like to do it :)
Mike
next reply other threads:[~2001-05-01 17:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 17:41 mike_phillips [this message]
-- 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 15:27 mike_phillips
2001-05-01 17:22 ` Linus Torvalds
2001-05-01 19:45 ` Russell King
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 7:26 ` Geert Uytterhoeven
2001-05-02 1:02 ` Paul Mackerras
2001-05-02 19:28 ` Benjamin Herrenschmidt
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=OF8F30DD01.CDAFFB0E-ON85256A3F.005BE8E3@urscorp.com \
--to=mike_phillips@urscorp.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®