public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: mike_phillips@urscorp.com, linux-kernel@vger.kernel.org,
	netdev@oss.sgi.com
Subject: Re: isa_read/write not available on ppc - solution suggestions ??
Date: Tue, 01 May 2001 10:50:57 -0400	[thread overview]
Message-ID: <3AEECD51.ABC493CB@didntduck.org> (raw)
In-Reply-To: <E14ubFe-0001jg-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > a) change everything to read/write and friends (the way the driver used to
> > be before the isa_read/write function were introduced)
> 
> readb/readw/readl have always worked for ISA bus. They simply avoid the need
> for ioremap and are meant for lazy porting

You meant isa_read* were for lazy porting.  read* require ioremap be
done before hand, even for ISA.

--

				Brian Gerst

  reply	other threads:[~2001-05-01 14:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01 13:52 isa_read/write not available on ppc - solution suggestions ?? 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 [this message]
2001-05-01 15:14     ` Alan Cox
2001-05-01 14:36 ` Brian Gerst
2001-05-01 17:33 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
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  1:02   ` Paul Mackerras
2001-05-02 19:28     ` Benjamin Herrenschmidt
2001-05-02  7:26   ` Geert Uytterhoeven
2001-05-01 17:41 mike_phillips
2001-05-02 13:12 mike_phillips
2001-05-03 11:08 ` Anton Blanchard

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=3AEECD51.ABC493CB@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike_phillips@urscorp.com \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox