All of lore.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: isa_read/write not available on ppc - solution suggestions ??
Date: 1 May 2001 10:22:39 -0700	[thread overview]
Message-ID: <9cmrcv$20e$1@penguin.transmeta.com> (raw)
In-Reply-To: <OF7A9C6B22.E1638E60-ON85256A3F.004EADC7@urscorp.com>

In article <OF7A9C6B22.E1638E60-ON85256A3F.004EADC7@urscorp.com>,
 <mike_phillips@urscorp.com> wrote:
>>mike_phillips@urscorp.com wrote:
>>> 
>>> To get the pcmcia ibmtr driver (ibmtr/ibmtr_cs) working on ppc, all the
>>> isa_read/write's have to be changed to regular read/write due to the 
>lack
>>> of the isa_read/write functions for ppc.
>
>> Treat it like a PCI device and use ioremap().  Then change isa_readl()
>> to readl() etc.
>
>Bleurgh, the latest version of the driver (not in the kernel yet) searches 
>for turbo based cards by checking the isa address space from 0xc0000 - 
>0xe0000 in 8k chunks. So we'd have to ioremap each 8k section, check it, 
>find out the adapter isn't there and then iounmap it. 
>
>Oh well, if that's what it takes =:0

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).

		Linus

  reply	other threads:[~2001-05-01 17:23 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 [this message]
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  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='9cmrcv$20e$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.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 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.