Hi,
On Fri, 27 Apr 2007 15:49:57 -0700, Greg KH wrote:
> Here are the updated UIO (Userspace I/O driver framework) patches for
> 2.6.21.
>
>
> Documentation/DocBook/kernel-api.tmpl | 4 +
> Documentation/DocBook/uio-howto.tmpl | 498 +++++++++++++++++++++++
> drivers/Kconfig | 1 + drivers/Makefile
> | 1 + drivers/uio/Kconfig | 27 ++
> drivers/uio/Makefile | 2 + drivers/uio/uio.c
> | 702 +++++++++++++++++++++++++++++++++
> drivers/uio/uio_cif.c | 156 ++++++++
> include/linux/uio_driver.h | 91 +++++ 9 files changed,
> 1482 insertions(+), 0 deletions(-) create mode 100644
> Documentation/DocBook/uio-howto.tmpl create mode 100644
> drivers/uio/Kconfig create mode 100644 drivers/uio/Makefile create mode
> 100644 drivers/uio/uio.c
> create mode 100644 drivers/uio/uio_cif.c create mode 100644
> include/linux/uio_driver.h
>
uio_dummy.c (that should be present according documentation) seems
missing.
I find the doc not very clear for the devices where there is no
interrupt : they speak of some kernel timer, but a userspace timer could
be used (and even the userspace driver could be written without kernel
support at all).
At the end of the doc there is something about IRQ_HANDLED vs IRQ_NONE.
Last time I check kernel irq code, in both case next irq handler are
called. The only difference was that if all handler reply IRQ_NONE, the
kernel gave an error about an unexpected interrupt.
Also why sysfs is used for describing the mapping instead of something
like an ioctl ?
UIO could be useful in embedded system where sysfs is not always
desirable.
Matthieu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
