On Wed, Oct 23, 2002 at 18:29:52 +0200, Henning Meier-Geinitz wrote:
> So the basic question is: Is there anything that the scanner driver
> can do that libusb can't and that's needed by any backend? Are there
> any other reasons to not remove the USB scanner driver in Linux some
> day in the futur
On Wed, Oct 23, 2002 at 18:11:16 +0100, Major A wrote:
>
> > Giving access to all USB devices is relatively simple: usbdevfs has
> > several mount options to control it: devuid, devgid, devmode; bus*,
> > list*.
>
> Oh, that's good to know. So far, I've only tried chmod, with no
> success...
chm
Hi,
On Thu, Oct 24, 2002 at 03:37:48PM +0400, Sergey Vlasov wrote:
> With the current implementation of sanei_usb, the libusb:* identifiers in
> SANE are not persistent - they change each time the scanner is
> disconnected and connected again. Because of this, saved preferences in
> the frontends
On Mittwoch, 23. Oktober 2002 18:29, Henning Meier-Geinitz wrote:
[SNIP]
> plustekwill need some work to autodetect all supported scanners
>(currently the approach is: check ids of /dev/usb/scanner fo=
r
> =09 everything we now)
Seems to be no problem at all, can be checked in af
On Wed, 23 Oct 2002 17:47:18 +0100
Major A wrote:
> How does libusb handle permissions on linux then? /proc/bus/usb can
> only be accessed by root. With the USB scanner module, one had a way
> of setting permissions via the device file.
Giving access to all USB devices is relatively simple: usbd
Hi,
On Wed, Oct 23, 2002 at 09:01:58PM +0400, Sergey Vlasov wrote:
> > How would one restrict access so that although a user can scan, they
> > can't fiddle with the USB hard drive or CD-ROM or automatic
> > nuclear-weapon detonator?
>
> This is trickier. Looks like the hotplug scripts are able t
Hi,
On Wed, Oct 23, 2002 at 06:21:50PM +0100, Jonathan Buzzard wrote:
> The other backends that spring to mind as using the scanner module are
> the hp backend, which uses the scanner backend,
Oh, that one doesn't even use sanei_usb. Changing that one will be a
bit more work. I didn't even know t
Hi,
On Wed, Oct 23, 2002 at 05:47:18PM +0100, Major A wrote:
> How does libusb handle permissions on linux then?
See man sane-usb :-)
> /proc/bus/usb can only be accessed by root.
On a one-user system: just mount it with read/write permissions for
everyone. On multiuser systems, use hot-plug ut
Hi,
While sending some questions and patches to the linux-usb-devel
mailing list, I was asked by Greg KH, the Linux USB maintainer:
| So the userspace SANE tools don't need the scanner driver anymore? If
| so, I'd be glad to remove the driver, like the others that we dropped a
| while ago for th
henn...@meier-geinitz.de said:
> The following backends seem to support USB scanners:
> canon630u looks like libusb-ready coolscan2 looks like libusb-ready
> epson already has a check for vendor/device ids but may need a way
>to search for all epson scanners automaticall
> mustek
> Giving access to all USB devices is relatively simple: usbdevfs has
> several mount options to control it: devuid, devgid, devmode; bus*,
> list*.
Oh, that's good to know. So far, I've only tried chmod, with no
success...
> You can give the "saned" user the right to access all USB devices.
Gre
> The background is, that there isn't a really good reason to have a
> generic driver for USB scanners in the kernel. There is no USB class
> for scanners, so the scanner driver must be constantly updated with
> new vendor and product ids. Furthermore, the scanner driver doesn't
> provide any funct
[ ... ]
> The following backends seem to support USB scanners:
[ ... ]
> epson already has a check for vendor/device ids but may need a way
>to search for all epson scanners automatically
I have this already working in my sandbox, I'm just waiting for 1.0.9 to
be released. Once I
13 matches
Mail list logo
