From: Frank v Waveren <fvw@var.cx>
To: Kernel Developer List <linux-kernel@vger.kernel.org>
Subject: Re: How do I access ioports from userspace?
Date: Fri, 26 Sep 2003 07:26:37 +0200 [thread overview]
Message-ID: <20030926052636.GA15006@var.cx> (raw)
In-Reply-To: <20030925160351.E26493@one-eyed-alien.net>
On Thu, Sep 25, 2003 at 04:03:51PM -0700, Matthew Dharm wrote:
> I'd like to be able to access some ioports to some custom hardware directly
> from userspace, without creating a specialized kernel-level driver. Is
> there a way to do that?
Either use /dev/port, or if it's performance critical (but not performance
critical enough to do in kernelspace), use ioperm/iopl and inb/outb.
--
Frank v Waveren Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|dse.nl] ICQ#10074100 1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx 7BD9 09C0 3AC1 6DF2
next prev parent reply other threads:[~2003-09-26 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 23:03 How do I access ioports from userspace? Matthew Dharm
2003-09-25 23:21 ` Greg KH
2003-09-26 5:26 ` Frank v Waveren [this message]
2003-09-26 7:27 ` Benjamin Herrenschmidt
2003-09-26 7:34 ` Frank v Waveren
2003-09-26 7:40 ` Benjamin Herrenschmidt
2003-09-26 8:29 ` Frank v Waveren
2003-09-26 8:56 ` Jes Sorensen
2003-09-28 23:07 ` Peter Chubb
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=20030926052636.GA15006@var.cx \
--to=fvw@var.cx \
--cc=linux-kernel@vger.kernel.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