On Mon, 20 Jul 2009 12:55:36 -0700
Greg KH wrote:
> On Mon, Jul 20, 2009 at 10:52:27PM +0300, Michael S. Tsirkin wrote:
> > On Mon, Jul 20, 2009 at 09:09:43PM +0200, Hans J. Koch wrote:
> > > On Mon, Jul 20, 2009 at 10:29:34AM +0300, Michael S. Tsirkin
> > > wrote:
> > > > This adds a generic uio
On Mon, Jul 20, 2009 at 10:52:27PM +0300, Michael S. Tsirkin wrote:
> On Mon, Jul 20, 2009 at 09:09:43PM +0200, Hans J. Koch wrote:
> > On Mon, Jul 20, 2009 at 10:29:34AM +0300, Michael S. Tsirkin wrote:
> > > This adds a generic uio driver that can bind to any PCI device. First
> > > user will be
On Mon, Jul 20, 2009 at 09:09:43PM +0200, Hans J. Koch wrote:
> On Mon, Jul 20, 2009 at 10:29:34AM +0300, Michael S. Tsirkin wrote:
> > This adds a generic uio driver that can bind to any PCI device. First
> > user will be virtualization where a qemu userspace process needs to give
> > guest OS ac
On Mon, Jul 20, 2009 at 10:29:34AM +0300, Michael S. Tsirkin wrote:
> This adds a generic uio driver that can bind to any PCI device. First
> user will be virtualization where a qemu userspace process needs to give
> guest OS access to the device.
>
> Interrupts are handled using the Interrupt Di
This adds a generic uio driver that can bind to any PCI device. First
user will be virtualization where a qemu userspace process needs to give
guest OS access to the device.
Interrupts are handled using the Interrupt Disable bit in the PCI command
register and Interrupt Status bit in the PCI stat
