From: Rene Rebe <rene@exactcode.de>
To: George Garvey <tmwg-sane@inxservices.com>
Cc: sane-devel <sane-devel@lists.alioth.debian.org>,
linux-kernel@vger.kernel.org, oliver@neukum.org,
torvalds@osdl.org, marcelo.tosatti@cyclades.com
Subject: Please remove hpusbscsi Was: [sane-devel] HP 7450C, hpusbscsi, permissions in Fedora Core 3
Date: Mon, 03 Jan 2005 20:15:25 +0100 [thread overview]
Message-ID: <41D999CD.80105@exactcode.de> (raw)
In-Reply-To: <20050102101258.GB8385@inxservices.com>
Hi,
we should remove hpusbscsi from the Kernel. It is long obsolete and very
unstable. I can send a patch for 2.4 and 2.6 (if needed) ;-)
George Garvey wrote:
> On Sat, Jan 01, 2005 at 10:11:30PM -0800, Thomas Frayne wrote:
...
> As far as I know, Rene has made it pretty clear he doesn't want to
> use hpusbscsi with the avision driver. He prefers libusb.
Yes. Hpusbscsi has many drawbacks. The major ones are:
- does not work with new scanners (that are designed for USB 2.0)
- it is highly instable (e.g. during an i/o error it locks up
quite easily and leaves the (usb sub-)system in a state that
needs a reboot ...
The later problem made me add the user-space i/o code to the
SANE/Avision backend, because I had to reboot my system every 5 minutes
during development ...
Yours,
--
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
http://www.exactcode.de | http://www.exactcode.de/t2
+49 (0)30 255 897 45
next parent reply other threads:[~2005-01-03 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1104646290.5821.99.camel@localhost.localdomain>
[not found] ` <20050102101258.GB8385@inxservices.com>
2005-01-03 19:15 ` Rene Rebe [this message]
2005-01-03 20:04 ` Please remove hpusbscsi Was: [sane-devel] HP 7450C, hpusbscsi, permissions in Fedora Core 3 Oliver Neukum
2005-01-04 17:48 ` Till Kamppeter
2005-01-04 14:31 ` Marcelo Tosatti
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=41D999CD.80105@exactcode.de \
--to=rene@exactcode.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=oliver@neukum.org \
--cc=sane-devel@lists.alioth.debian.org \
--cc=tmwg-sane@inxservices.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox