I'll just toss two complications out:
- There are multiple user space tools that need to be taught
about how to do this. "OpenDIS" users seem to regularly
send in patches/thanks, rather than using "gphoto2".
(I suspect partly because of stability issues...)
- Security/permissions with "usbdevfs" aren't as manageable
as with /dev/usb/dc2xx files. That's a general problem for
hotpluggable devices, and I suspect solving it will come a
bit later in the 2.5 series.
When both those issues have good resolutions, _then_ it'll
be practical to make that driver go away.
By the way, at 3KBytes size doesn't seem like a compelling
issue ... certainly saving it isn't as much of a win as avoiding
worsening the two problems mentioned above, IMHO.
- Dave
----- Original Message -----
From: "Greg KH" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, December 01, 2001 6:36 PM
Subject: Re: [linux-usb-devel] on dc2xx
> On Sat, Dec 01, 2001 at 06:40:32PM +0100, Oliver Neukum wrote:
> > Hi,
> >
> > is there any reason this driver could not be put into scanner.c ?
> > This would IMO allow the most painless migration and decrease kernel size.
>
> It's actually going to be removed altogether, once people verify that
> the userspace implementation works properly.
>
> thanks,
>
> greg k-h
>
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
