https://bugzilla.novell.com/show_bug.cgi?id=382744
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=382744#c5
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #5 from Johannes Meixner 2008-04-29 00:08:38 MST ---
I didn't consider to make "Yast ignore anything that has
a kernel driver bound to it".
How could I implement such a functionality reliably?
I would prefer a generic method and not e.g. a hardcoded
list of certain kernel driver names which may change
for different kernel versions.
Isn't there always a kernel driver used for any device I/O?
For usual USB scanners usbfs/libusb is used at least
when the scanner is actively scanning.
For all-in-one devices there might be usblp bound to it when the
printer unit is used via /dev/usb/lp* (this results a conflict
with usbfs/libusb but it does actually happen, see bug #184825).
Furthermore a scanner driver can implement whatever it likes
to do the device access (i.e. it may not use libusb for USB
scanners but anything else).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.