Hello
"Dunlap, Randy" wrote:
> I see one good reason to keep these 3 drivers (and maybe scanner ?)
> in the kernel right now: user satisfaction. I'm trying to be
> realistic and pragmatic, not idealistic.
Yes, at the moment that's the only reason for me putting this driver
(mdc800) into
the Kernel. With the driver in the Kernel it is very easy to get a Mustek
MDC800
working with gphoto (with USB) (and the only way).
> Henning Zabel: what is keeping you from making the mdc800
> driver a userspace-only solution?
Nothing except that the camera needs an irq. I can't emulate an irq by
sometimes polling from the irq line with a bulk request. It has to be a
periodic
request else the camera behaves mysterious ?!
I have a USB driver for gphoto 0.5 that's uses the libgpio with the libusb
from Johannes,
but i have stopped the development at the moment, because i'm waiting for
an irq solution.
When i understand the philosophy of signals right it would be stable
solution (for the Kernel)
when you can request a signal from the usbdevfs thats post the data coming
thru the irq
to a program in userspace ?.
Abstract: When i can use a irq with the usbdevfs it will be a short hack
and the
Userspace driver is ready. And then the mdc800 should be removed from the
Kernel.
I also think that the mdc800 should not be in Kernel 2.5.
Henning
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
