[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081124090412.GA3086@local>
Date: Mon, 24 Nov 2008 10:04:12 +0100
From: "Hans J. Koch" <hjk@...utronix.de>
To: Greg KH <gregkh@...e.de>
Cc: "Hans J. Koch" <hjk@...utronix.de>, linux-kernel@...r.kernel.org,
Mike Frysinger <vapier@...too.org>,
John Ogness <jogness@...utronix.de>,
Benedikt Spranger <b.spranger@...utronix.de>
Subject: Re: [PATCH RFC] UIO: Pass information about ioports to userspace
On Sun, Nov 23, 2008 at 05:41:22PM -0800, Greg KH wrote:
> 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 :)
Not forgotten, just delayed :-)
We had other changes lately that need documentation update as well. Big patch
will come Real Soon Now...
thanks,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists