[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061214175448.GA24328@kroah.com>
Date: Thu, 14 Dec 2006 09:54:48 -0800
From: Greg KH <greg@...ah.com>
To: Avi Kivity <avi@...o.co.il>
Cc: arjan@...radead.org, linux-kernel@...r.kernel.org,
tglx@...utronix.de
Subject: Re: Userspace I/O driver core
On Thu, Dec 14, 2006 at 12:56:29PM +0200, Avi Kivity wrote:
> Arjan van de Ven wrote:
> >On Thu, 2006-12-14 at 12:46 +0200, Avi Kivity wrote:
> >
> >>Arjan van de Ven wrote:
> >>
> >>>>I understand one still has to write a kernel driver to shut up the irq.
> >>>>How about writing a small bytecode interpreter to make event than
> >>>>unnecessary?
> >>>>
> >>>>
> >>>if you do that why not do a real driver.
> >>>
> >>>
> >>>
> >>An entire driver in bytecode?
> >>
> >
> >no a real, non-bytecode driver.
> >
> >
>
> Isn't the whole point of uio is to avoid writing a kernel mode driver?
No. Did you read the documentation that is written about the uio core?
> As proposed, it doesn't quite accomplish it. With an additional
> bytecode interpreter, you can have a 100% userspace driver (the bytecode
> interpreter would be part of uio, not the driver).
If you want to try to work on something as complex as a bytecode
interpreter that can handle all of the hookups to the pci and other
kernel subsystems that are necessary to get such a driver to work
properly, feel free to.
But until then, you'll have to stick with a tiny kernelspace driver that
handles the basic hardware discovery and initialization logic.
Which, for everyone that I have talked to that needs such a driver, is
not a problem at all.
thanks,
greg k-h
-
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