From: antirez <antirez@invece.org>
To: Greg KH <greg@wirex.com>, Heitzso <xxh1@cdc.gov>,
"'antirez@invece.org'" <antirez@invece.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'Johannes Erdfelt'" <johannes@erdfelt.com>
Subject: Re: USB broken in 2.4.0
Date: Sat, 6 Jan 2001 00:04:29 +0100 [thread overview]
Message-ID: <20010106000429.K7784@prosa.it> (raw)
In-Reply-To: <B7F9A3E3FDDDD11185510000F8BDBBF2049E7F99@mcdc-atl-5.cdc.gov> <20010105100040.A25217@wirex.com>
In-Reply-To: <20010105100040.A25217@wirex.com>; from greg@wirex.com on Fri, Jan 05, 2001 at 10:00:40AM -0800
On Fri, Jan 05, 2001 at 10:00:40AM -0800, Greg KH wrote:
> I made the same request to Jordan Mendelson yesterday, who has the same
> problem. Could you be so kind as to try to narrow down which kernel
> version this broke on? I have reports that it used to work on -test9
> but doesn't now. Could you try -test10, etc and let me know?
I'll do some test with the new 2.4 kernel to find if there is a problem
in s10sh itself. A good test can be to try if the equivalent driver
of gphoto works without problems using the 2.4 kernel (however it also
uses the libusb). The s10sh bug may be not necessarly related to the USB
subsystem.
regards,
antirez
--
Salvatore Sanfilippo | <antirez@invece.org>
http://www.kyuzz.org/antirez | PGP: finger antirez@tella.alicom.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:38 USB broken in 2.4.0 Heitzso
2001-01-05 18:00 ` Greg KH
2001-01-05 23:04 ` antirez [this message]
2001-01-06 2:39 ` antirez
2001-01-06 3:40 ` antirez
-- strict thread matches above, loose matches on Subject: below --
2001-01-06 0:48 Dunlap, Randy
2001-01-06 3:50 ` antirez
2001-01-06 1:53 ` Johannes Erdfelt
2001-01-08 15:38 Heitzso
2001-01-08 17:54 ` antirez
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=20010106000429.K7784@prosa.it \
--to=antirez@invece.org \
--cc=greg@wirex.com \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xxh1@cdc.gov \
/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