From: Greg KH <greg@kroah.com>
To: Stian Jordet <liste@jordet.nu>
Cc: Azog <slashmail@arnor.net>, 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: Thu, 5 Feb 2004 09:57:52 -0800 [thread overview]
Message-ID: <20040205175752.GD13075@kroah.com> (raw)
In-Reply-To: <1076003405.9101.2.camel@chevrolet.hybel>
On Thu, Feb 05, 2004 at 06:50:06PM +0100, Stian Jordet wrote:
> tor, 05.02.2004 kl. 18.30 skrev Greg KH:
> > On Thu, Feb 05, 2004 at 09:20:58AM -0800, Azog wrote:
> > >
> > > So, what are you all using / recommending for user space configuration
> > > and control of a USB scanner under 2.6?
> >
> > xsane should work just fine, using libusb/usbfs.
> >
> > As this driver is no longer needed, and the driver is broken and no one
> > has stepped up to fix it for over a month now, I'm removing it from the
> > kernel tree.
>
>
> I know it is broken, and obsoleted. But for those of us not using
> hotplug scripts, it's quite a pity that you have to manually chmod the
> files in /proc/bus/usb to be able to use a device with libusb as a
> normal user. Just want to let people having trouble know that.
Or fix this bug:
http://bugme.osdl.org/show_bug.cgi?id=1418
That will make it easier for users too.
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-05 18:00 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 [this message]
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
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=20040205175752.GD13075@kroah.com \
--to=greg@kroah.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=liste@jordet.nu \
--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