From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: "Andrew S. Johnson" <andy@asjohnson.com>
Cc: Harald Arnesen <harald@skogtun.org>, linux-kernel@vger.kernel.org
Subject: Re: Oops with USB scanner in 2.6.2
Date: Thu, 05 Feb 2004 15:48:14 +0100 [thread overview]
Message-ID: <402257AE.6070902@gmx.de> (raw)
In-Reply-To: <200402050732.01636.andy@asjohnson.com>
Andrew S. Johnson wrote:
> On Thursday 05 February 2004 04:56 am, Prakash K. Cheemplavam wrote:
>
>>Harald Arnesen wrote:
>>
>>>"Andrew S. Johnson" <andy@asjohnson.com> writes:
>>>
>>>
>>>
>>>>This didn't happen with 2.4.22. The scanner works OK until I turn it off.
>>>>Then I get the oops. rmmod scanner hangs, with and without the -f switch.
>>>
>>>
>>>I just want to confirm that the same thing happens here.
>>
>>You shouldn't use it anymore. Use libusb.
>>
>>Prakash
>>
>
> Use what anymore?
Don't use the scanner module. Use libusb (and hotplug) to access the
scanner.
Prakash
prev parent reply other threads:[~2004-02-05 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 4:33 Oops with USB scanner in 2.6.2 Andrew S. Johnson
2004-02-05 9:23 ` Harald Arnesen
2004-02-05 10:56 ` Prakash K. Cheemplavam
2004-02-05 13:32 ` Andrew S. Johnson
2004-02-05 14:48 ` Prakash K. Cheemplavam [this message]
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=402257AE.6070902@gmx.de \
--to=prakashkc@gmx.de \
--cc=andy@asjohnson.com \
--cc=harald@skogtun.org \
--cc=linux-kernel@vger.kernel.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