From: Paul Mackerras <paulus@cs.anu.edu.au>
To: drow@false.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ioremap() on ISA memory space
Date: Wed, 9 Jun 1999 11:06:46 +1000 [thread overview]
Message-ID: <199906090106.LAA05407@tango.anu.edu.au> (raw)
In-Reply-To: <19990608161648.A7950@drow.res.cmu.edu> (message from Daniel Jacobowitz on Tue, 8 Jun 1999 16:16:49 -0400)
Daniel Jacobowitz <drow@false.org> wrote:
> When I was hacking on tulip.c, I wanted to use tulip-daig to get the
> state of the card. But it uses inl/outl, and on powerpc these have a
> kernel private variable (isa_io_base) in their macro expansion. Is
> there any way to make the PCI space available to userland on powerpc,
> as iopl() and inb/outb can on x86?
You have to open /dev/mem and do a mmap of the physical pages for the
PCI I/O space. You would then need to have a variable called
isa_io_base and put the address you get back from mmap into it.
PCI I/O space is usually at 0xf2000000 on older powermacs. If you
want to get fancy, you can wander through /proc/device-tree looking
for the primary PCI bridge and use that to work out where the I/O
space is.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-06-09 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-08 18:28 ioremap() on ISA memory space Geert Uytterhoeven
1999-06-08 19:08 ` Gabriel Paubert
1999-06-08 20:16 ` Daniel Jacobowitz
1999-06-09 1:06 ` Paul Mackerras [this message]
1999-06-09 7:38 ` Geert Uytterhoeven
1999-06-09 7:41 ` Geert Uytterhoeven
1999-06-10 8:30 ` 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=199906090106.LAA05407@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=drow@false.org \
--cc=linuxppc-dev@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).