public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: gene.heskett@verizon.net
Cc: Azog <slashmail@arnor.net>, Greg KH <greg@kroah.com>,
	Adrian Bunk <bunk@fs.tum.de>,
	Tom Rini <trini@kernel.crashing.org>,
	Andre Noll <noll@mathematik.tu-darmstadt.de>,
	Linux-Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] remove USB_SCANNER
Date: Fri, 06 Feb 2004 15:59:09 -0500	[thread overview]
Message-ID: <4024001D.80308@tmr.com> (raw)
In-Reply-To: <200402052015.22926.gene.heskett@verizon.net>

Gene Heskett wrote:
> On Thursday 05 February 2004 12:20, Azog wrote:
> 
>>On Wed, 2004-02-04 at 17:14, Greg KH wrote:
>>
>>>On Thu, Feb 05, 2004 at 01:31:36AM +0100, Adrian Bunk wrote:
>>
>>[...]
>>
>>
>>>>If not, please apply the patch below plus do a
>>>>  rm drivers/usb/image/scanner.{c,h}
>>>
>>>I've applied this patch, and removed the driver from the kernel.
>>
>>(sigh) Just last night I had to reboot into 2.4 to use my new USB
>>scanner.
>>
>>I tried for a while to get it working under 2.6.  I'm not exactly a
>>beginner at this stuff either.
>>
>>With 2.4 it took less than 30 seconds and worked perfectly,
>>following the SANE documentation instructions.  My user space is
>>Fedora Core 1 with all available updates.
>>
>>So, what are you all using / recommending for user space
>>configuration and control of a USB scanner under 2.6?
>>
>>http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt doesn't say
>>a word about USB scanners, and I havn't seen the issue mentioned
>>anywhere else either.
>>
> 
> I dunno what the problem might be on your mobo, but here, the latest 
> version of libusb (1.7 I believe) "just works" with virtually any 2.6 
> kernel so far.  You may want to turn on the verbose debugging in 
> your .config file, rebuild and reboot.  It might be educational.
> 
I think the problem is not that it doesn't work with kernel, but it 
doesn't work with the application. And while some people may be able to 
ignore having a system which will work with both 2.4 and 2.6 kernels, 
for many systems it may not be practical to change config to something 
which will not work in 2.4 in hopes it might work in 2.6.

Marking the old driver as broken is fine, taking it out will certainly 
prevent anyone from fixing it. Better to have it around, I would think.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  reply	other threads:[~2004-02-06 20:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 21:50 [ANNOUNCE] udev 015 release Greg KH
2004-01-26 22:15 ` Tomasz Torcz
2004-01-27  5:52 ` Chris Friesen
2004-01-27 22:22   ` Greg KH
2004-01-29  4:52 ` Martin Schlemmer
2004-01-29 21:54   ` Greg KH
2004-01-29 16:52 ` Martin Schlemmer
2004-01-29 21:55   ` Greg KH
2004-01-31  3:17     ` Kay Sievers
2004-01-31 17:54       ` Martin Schlemmer
2004-01-31 18:15         ` Kay Sievers
2004-01-31 18:27           ` Martin Schlemmer
2004-01-31 18:39             ` Kay Sievers
2004-01-31 18:47               ` Martin Schlemmer
2004-01-29 18:30 ` Martin Schlemmer
2004-01-30  4:41   ` Martin Schlemmer
2004-02-02 23:32   ` Greg KH
2004-02-03  4:12     ` Martin Schlemmer
2004-01-30 16:45 ` Prakash K. Cheemplavam
2004-01-30 17:23   ` Greg KH
2004-01-30 17:44     ` Prakash K. Cheemplavam
2004-01-30 17:49       ` Greg KH
2004-01-30 18:17         ` Prakash K. Cheemplavam
2004-02-01 15:24     ` Martin Schlemmer
2004-02-02  8:46       ` Prakash K. Cheemplavam
2004-01-30 17:33   ` Martin Schlemmer
2004-01-30 18:03   ` Andre Noll
2004-01-30 23:06     ` Tom Rini
2004-02-02 21:43       ` Greg KH
2004-02-05  0:31         ` [2.6 patch] remove USB_SCANNER Adrian Bunk
2004-02-05  1:14           ` Greg KH
2004-02-05 17:20             ` Azog
2004-02-05 17:30               ` Greg KH
2004-02-05 17:50                 ` Stian Jordet
2004-02-05 17:57                   ` Greg KH
2004-02-05 20:24                 ` Leopold Gouverneur
2004-02-05 21:15                   ` Stian Jordet
2004-02-05 21:36                     ` Leopold Gouverneur
2004-02-06  1:15               ` Gene Heskett
2004-02-06 20:59                 ` Bill Davidsen [this message]
2004-02-06 21:04                   ` Greg KH
2004-02-01 22:52 ` hal daemon and ide-floppy J.A. Magallon
2004-02-02  3:16   ` Greg KH
2004-02-02 22:32 ` udev depends on /usr J.A. Magallon
2004-02-02 22:44   ` Greg KH
2004-02-02 23:01     ` J.A. Magallon
2004-02-03  4:10     ` Martin Schlemmer
2004-02-02 23:08 ` [ANNOUNCE] udev 015 release Prakash K. Cheemplavam
2004-02-02 23:11   ` Greg KH

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=4024001D.80308@tmr.com \
    --to=davidsen@tmr.com \
    --cc=bunk@fs.tum.de \
    --cc=gene.heskett@verizon.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noll@mathematik.tu-darmstadt.de \
    --cc=slashmail@arnor.net \
    --cc=trini@kernel.crashing.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