On Thu, Apr 29, 2010 at 12:29:40PM -0700, Tom Lyon wrote:
Michael, et al - sorry for the delay, but I've been digesting the comments
and researching new approaches.
I think the plan for V4 will be to take things entirely out of the UIO
framework, and instead have a driver which supports
On Thu, Apr 29, 2010 at 12:29:40PM -0700, Tom Lyon wrote:
I think the plan for V4 will be to take things entirely out of the UIO
framework, and instead have a driver which supports user mode use of
well-behaved PCI devices.
I really don't think that we should create another uio-subsystem for
On Thu, Apr 29, 2010 at 12:29:40PM -0700, Tom Lyon wrote:
Michael, et al - sorry for the delay, but I've been digesting the comments
and researching new approaches.
I think the plan for V4 will be to take things entirely out of the UIO
framework, and instead have a driver which supports
Michael, et al - sorry for the delay, but I've been digesting the comments and
researching new approaches.
I think the plan for V4 will be to take things entirely out of the UIO
framework, and instead have a driver which supports user mode use of
well-behaved PCI devices. I would like to use
On Mon, Apr 19, 2010 at 03:05:35PM -0700, Tom Lyon wrote:
These are changes to uio_pci_generic.c to allow better use of the driver by
non-privileged processes.
1. Add back old code which allowed interrupt re-enablement through uio fd.
2. Translate PCI bards to uio mmap regions, to allow mmap
On Wed, Apr 21, 2010 at 12:38:49PM +0300, Michael S. Tsirkin wrote:
+ j++;
+ }
+ }
+ for (i = 0, j = 0; i PCI_STD_RESOURCE_END
+ j MAX_UIO_PORT_REGIONS; i++) {
+ if (pci_resource_flags(pdev, i) IORESOURCE_IO) {
+
On Wed, Apr 21, 2010 at 12:31:50PM +0200, Hans J. Koch wrote:
On Wed, Apr 21, 2010 at 12:38:49PM +0300, Michael S. Tsirkin wrote:
+ j++;
+ }
+ }
+ for (i = 0, j = 0; i PCI_STD_RESOURCE_END
+j MAX_UIO_PORT_REGIONS; i++) {
+
These are changes to uio_pci_generic.c to allow better use of the driver by
non-privileged processes.
1. Add back old code which allowed interrupt re-enablement through uio fd.
2. Translate PCI bards to uio mmap regions, to allow mmap through uio fd.
3. Allow devices which support MSI or MSI-X,
