linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: map iomem in linux_2_4_dev
Date: Mon, 27 May 2002 16:34:51 +1000	[thread overview]
Message-ID: <20020527063451.GL16537@zax> (raw)
In-Reply-To: <003801c20543$b90a4180$e1a8459b@ntu.edu.sg>


On Mon, May 27, 2002 at 01:59:54PM +0800, shaowei dai wrote:
>
> Hello, every one:
>
> I've searched through the achieve, but failed to find stuff about mapping
> io-memmory in this linux_2_4_dev version.
> After check the source code, it seems from 2_4_dev onwards, no need to use
> ioremap to map io memory. We
> should use io_block_mapping() instead.

No, you should use ioremap() wherever possible.  Only use
io_block_mapping() if for some strange reason you need to specify the
virtual address.

--
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-05-27  6:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27  5:59 map iomem in linux_2_4_dev shaowei dai
2002-05-27  6:34 ` David Gibson [this message]
2002-05-27  6:51   ` shaowei dai
2002-05-27  8:13     ` Sangmoon Kim
2002-05-27  8:13       ` shaowei dai
2002-05-28  0:36         ` David Gibson
2002-05-28  4:42           ` Sangmoon Kim
  -- strict thread matches above, loose matches on Subject: below --
2002-05-28 10:38 Sangmoon Kim
2002-05-28 13:23 ` Matt Porter
2002-05-29  4:57   ` Sangmoon Kim
2002-05-29  5:47     ` Roland Dreier
2002-05-29  6:01       ` Sangmoon Kim
2002-05-29  5:47     ` David Gibson
2002-05-29  6:14       ` Sangmoon Kim
2002-05-29 12:48       ` shaowei dai

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=20020527063451.GL16537@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-embedded@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).