All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Koeller <thomas.koeller@baslerweb.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linux-mips@linux-mips.org
Subject: Re: ioremap() and CONFIG_SWAP_IO_SPACE
Date: Tue, 19 Oct 2004 20:31:05 +0200	[thread overview]
Message-ID: <20041019183105.GB9379@linux-mips.org> (raw)
In-Reply-To: <200410191245.59878.thomas.koeller@baslerweb.com>

On Tue, Oct 19, 2004 at 12:45:59PM +0200, Thomas Koeller wrote:

> Well, the ioremap() man page uses the term 'bus memory';
> there is no reference to PCI at all. I guess there could
> be multiple buses on one machine with different byte swapping
> requirements? There is also an article written by alan cox
> (http://www.kernelnewbies.org/documents/kdoc/deviceiobook.pdf)
> that describes ioremap() as a general mechanism of accessing
> memory-mapped io devices, with no reference to PCI at all.
> 
> Anyway, if ioremap() and readx()/writex() are for PCI memory
> access only, how am I supposed to access memory-mapped io
> devices that are not on a PCI bus?

If the standard readX() / writeX() functions don't suffice for some reason
then a bus specific versions in a separate header file are needed.

An example are the ISA versions.  For compatibility with super old
versions from before ioremap or where things on i386 at least seemed to
work without ioremap a special isa_readX() / isa_writeX() is supplied.
Again for compatibility reasons these macros are defined in <asm/io.h>,
not in a separate header file.

> Basler Vision Technologies
> An der Strusbek 60-62
> 22926 Ahrensburg
> Germany

Oh, not in Basel :-)

  Ralf

  reply	other threads:[~2004-10-19 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  9:30 ioremap() and CONFIG_SWAP_IO_SPACE Thomas Koeller
2004-08-25  9:32 ` Geert Uytterhoeven
2004-10-19 10:45   ` Thomas Koeller
2004-10-19 18:31     ` Ralf Baechle [this message]
2004-10-20  8:47       ` Thomas Koeller

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=20041019183105.GB9379@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=thomas.koeller@baslerweb.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.