From: Greg KH <gregkh@suse.de>
To: "Hans J. Koch" <hjk@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>,
John Ogness <jogness@linutronix.de>,
Benedikt Spranger <b.spranger@linutronix.de>
Subject: Re: [PATCH RFC] UIO: Pass information about ioports to userspace
Date: Sun, 23 Nov 2008 17:41:22 -0800 [thread overview]
Message-ID: <20081124014122.GB14143@suse.de> (raw)
In-Reply-To: <20081123121419.GA3087@local>
On Sun, Nov 23, 2008 at 01:14:20PM +0100, Hans J. Koch wrote:
> Devices sometimes have memory where all or parts of it can not be mapped to
> userspace. But it might still be possible to access this memory from
> userspace by other means. An example are PCI cards that advertise not only
> mappable memory but also ioport ranges. On x86 architectures, these can be
> accessed with ioperm, iopl, inb, outb, and friends. Mike Frysinger (CCed)
> reported a similar problem on Blackfin arch where it doesn't seem to be easy
> to mmap non-cached memory but it can still be accessed from userspace.
>
> This patch allows kernel drivers to pass information about such ports to
> userspace. Similar to the existing mem[] array, it adds a port[] array to
> struct uio_info. Each port range is described by start, size, and porttype.
Looks good, but I think you also forgot the documentation update :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-24 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 12:14 [PATCH RFC] UIO: Pass information about ioports to userspace Hans J. Koch
2008-11-24 1:40 ` Greg KH
2008-11-24 10:19 ` Hans J. Koch
2008-11-25 4:11 ` Greg KH
2008-11-25 23:56 ` Hans J. Koch
2008-11-24 1:41 ` Greg KH [this message]
2008-11-24 9:04 ` Hans J. Koch
2008-12-06 1:23 ` [PATCH 1/2] UIO: Pass information about ioports to userspace (V2) Hans J. Koch
2008-12-06 1:25 ` [PATCH 2/2] UIO: Documentation for UIO ioport info handling Hans J. Koch
2008-12-22 19:03 ` Randy Dunlap
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=20081124014122.GB14143@suse.de \
--to=gregkh@suse.de \
--cc=b.spranger@linutronix.de \
--cc=hjk@linutronix.de \
--cc=jogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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