From: Tom Rini <trini@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
henning@meier-geinitz.de,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb-users@lists.sourceforge.net
Subject: Re: USB scanner issue (Was: Re: Beaver in Detox!)
Date: Mon, 1 Dec 2003 13:52:16 -0700 [thread overview]
Message-ID: <20031201205216.GA4307@stop.crashing.org> (raw)
In-Reply-To: <20031201192158.GC23209@kroah.com>
On Mon, Dec 01, 2003 at 11:21:58AM -0800, Greg KH wrote:
> On Fri, Nov 28, 2003 at 11:26:25AM -0700, Tom Rini wrote:
> > On Wed, Nov 26, 2003 at 12:55:00PM -0800, Linus Torvalds wrote:
> >
> > [snip]
> > > I give you "Beaver in Detox", aka linux-2.6.0-test11. This is mainly
> > > brought on by the fact that the old aic7xxx driver was broken in -test10,
> > > and Ingo found this really evil test program that showed an error case in
> > > do_fork() that we had never handled right. Well, duh!
> >
> > I've found an odd problem that's in at least 2.6.0-test11. I've
> > reproduced this twice now with an Epson 1240 USB scanner
> > (0x04b8/0x010b). What happens is if I run xsane from gimp, acquire a
> > preview, start to scan and then cancel, the scanner becomes
> > unresponsive. If I try and quit xsane, it gets stuck. Unplugging /
> > replugging and then trying to kill xsane locked the machine up hard.
> >
> > Here's ver_linux, dmesg and the versions of gimp/xsane I'm running (I've
> > used the scanner during this boot, without trying to lock it up):
>
> Can't you use xsane without the scanner kernel driver? I thought the
> latest versions used libusb/usbfs to talk directly to the hardware.
> Because of this, the USB scanner driver is marked to be removed from the
> kernel sometime in the near future.
After a bit of mucking around (and possibly finding a bug with debian's
libusb/xsane/hotplug interaction, nothing seems to run
/etc/hotplug/usb/libusbscanner and thus only root can scan, anyone whose
got this working please let me know), the problem does not exist if I
only use libusb xsane.
How about the following:
===== drivers/usb/image/Kconfig 1.5 vs edited =====
--- 1.5/drivers/usb/image/Kconfig Thu Sep 25 11:22:48 2003
+++ edited/drivers/usb/image/Kconfig Mon Dec 1 13:51:48 2003
@@ -18,12 +18,14 @@
module will be called mdc800.
config USB_SCANNER
- tristate "USB Scanner support"
+ tristate "USB Scanner support (OBSOLETE)"
depends on USB
help
Say Y here if you want to connect a USB scanner to your computer's
USB port. Please read <file:Documentation/usb/scanner.txt> for more
information.
+
+ This driver has been obsoleted by support via libusb.
To compile this driver as a module, choose M here: the
module will be called scanner.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2003-12-01 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 20:55 Beaver in Detox! Linus Torvalds
2003-11-26 22:00 ` Rik van Riel
2003-11-27 0:20 ` Beaver in Detox! (compile stats) John Cherry
2003-11-28 18:26 ` USB scanner issue (Was: Re: Beaver in Detox!) Tom Rini
2003-12-01 19:21 ` Greg KH
2003-12-01 20:52 ` Tom Rini [this message]
2003-12-09 17:41 ` Greg KH
2003-12-06 18:49 ` [Linux-usb-users] " Henning Meier-Geinitz
2003-12-07 4:48 ` Tom Rini
2003-12-07 10:21 ` [Linux-usb-users] " Henning Meier-Geinitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031201205216.GA4307@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=henning@meier-geinitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.