From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <jeffrey.d.kowing1@jsc.nasa.gov>,
Hollis Blanchard <hollis@austin.ibm.com>
Cc: <jeffrey.d.kowing1@jsc.nasa.gov>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: io.h and I/O port access from user space
Date: Tue, 5 Feb 2002 23:34:46 +0100 [thread overview]
Message-ID: <20020205223446.15657@smtp.wanadoo.fr> (raw)
In-Reply-To: <15456.23060.255087.831957@igor.jsc.nasa.gov>
>
>
>Well, since you ask and at the risk of further demonstrating my
>ignorance:
>
>Yes, I have ISA slots - well, actually, I have a PC/104 stack.
>
>Specifically, I've got an inhouse 603ev/MPC106 board on a PC/104 form
>factor running a linuxppc 2.4.x kernel. I've been using an Adastra
>NSP-104 PC/104 module as my network interface card. That card,
>besides its ethernet chip, also has a Super I/O PC87338 chip that
>controls two serial ports (i.e. SCC1 and SCC2). Naturally, I just had
>to use those two serial ports, and, of course, it doesn't have nice
>little jumpers to set IRQ and IO base addresses. Instead, it wants to
>be configured using Plug-n-Play which I obviously know nothing about.
>Anyways, I thought, hey, I'll investigate by using this nifty
>isapnptools package. Silly me.
>
>But beyond my specific problem, I guess it got me to wondering in
>general about the proper way to write user space programs using
>inb/outb (and in my wildest fantasies of submiting a patch for
>isapnptools).
The best way here is to use the mmap facility of /proc/bus/pci to
mmap the IO space of the bus into your userland space, and then
write your own accessors.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 22:34 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
2002-02-05 22:17 ` Jeffrey D. Kowing
2002-02-05 22:34 ` Benjamin Herrenschmidt [this message]
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=20020205223446.15657@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=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 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).