From: Hollis Blanchard <hollis@austin.ibm.com>
To: jeffrey.d.kowing1@jsc.nasa.gov
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: io.h and I/O port access from user space
Date: 05 Feb 2002 15:48:10 -0600 [thread overview]
Message-ID: <1012945690.1265.11.camel@granite> (raw)
In-Reply-To: <15456.16854.183292.343027@igor.jsc.nasa.gov>
On Tue, 2002-02-05 at 14:34, Jeffrey D. Kowing wrote:
>
> Is there suppose to be a <sys/io.h> for powerpc platforms ?
I guess not. I'm not a glibc person though...
> What include file should I use to get inb/outb defined for a user
> space program. (This is a linuxppc 2.4.x kernel I'm working with.)
I'm not sure there are any.
> I guess it is still the case for the linuxppc-2.4.x series that I need
> to mmap /dev/mem first as per Geert's advice in
> http://lists.linuxppc.org/linuxppc-dev/200003/msg00076.html advice?
Yes, you certainly need to mmap /dev/mem.
> Has anyone in powerpc land used the isapnptools ?
I guess the obvious question is do you have ISA slots in the system
you're trying to build for? And you don't want to use the in-kernel
stuff? Do you really *need* isapnptools? :)
If you have ISA, it's probably a PReP? I've done user space IO simply by
mmap'ing (offset = 0x80000000), then just doing accesses normally:
(char *)ioregion = mmap(...)
ioregion[0x3fc] = 0x1;
etc.
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 20:34 io.h and I/O port access from user space Jeffrey D. Kowing
2002-02-05 21:26 ` Jeffrey D. Kowing
2002-02-05 21:48 ` Hollis Blanchard [this message]
2002-02-05 22:17 ` Jeffrey D. Kowing
2002-02-05 22:34 ` Benjamin Herrenschmidt
2002-02-05 23:07 ` Hollis Blanchard
2002-02-06 0:16 ` Jeffrey D. Kowing
2002-02-06 10:37 ` 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=1012945690.1265.11.camel@granite \
--to=hollis@austin.ibm.com \
--cc=jeffrey.d.kowing1@jsc.nasa.gov \
--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 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.