From: Wes Janzen <superchkn@sbcglobal.net>
To: David Brownell <david-b@pacbell.net>
Cc: Michael Guterl <mguterl@gmail.com>,
linux-usb-devel@lists.sourceforge.net,
Luis Miguel Garc Mancebo <ktech@wanadoo.es>,
Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>,
akpm@osdl.org
Subject: Re: [linux-usb-devel] Re: USB troubles in rc2
Date: Sat, 07 Aug 2004 17:01:28 -0500 [thread overview]
Message-ID: <41155138.4090707@sbcglobal.net> (raw)
In-Reply-To: <200408071051.23047.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
David Brownell wrote:
>On Thursday 05 August 2004 10:05, Michael Guterl wrote:
>
>
>>Thanks for the reply David, but where exactly does this leave me and
>>the others experiencing this problem? Is there any more information I
>>can provide that might help? Any possible solutions, patches, etc?
>>
>>
>
>It leaves you (and others) with the problem partially isolated, so that
>someone with time to track it down will have that much less work to do.
>[...]
>A third-best would be for someone (you?) to find out exactly which patch
>caused the problem -- a binary search of the USB patches, luckily it's
>made easier by the fact that it could only be a change in HID, usbcore,
>or some HCD. (And most likely IMO it's usbcore.) Then that patch can
>either be further debugged, or reverted.
>
>- Dave
>
>
>
OK, I'm willing since I'm stuck with 2.6.7-ck5 which eventually bugs due
to some USB problems. I'm not a developer so I need a little help
learning how to get the USB patches added somewhere in between 2.6.7 and
2.6.7-mm2/2.6.8-rc1. I'm kinda busy right now so maybe I didn't search
the kernel.org website well enough, but I've reached the conclusion I'll
need to use bk or the cvs interface. So if someone can give me a quick
and dirty tutorial or point me to where I can read up on this (or just
give me some google search terms) I'd be willing to apply patches until
it breaks and try to figure out what's going wrong.
Thanks,
Wes
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-07 22:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 19:00 USB troubles in rc2 Luis Miguel García Mancebo
2004-08-03 0:26 ` Greg KH
2004-08-03 2:08 ` Michael Guterl
2004-08-03 6:49 ` Trever L. Adams
2004-08-03 8:46 ` Luis Miguel García Mancebo
2004-08-03 13:57 ` Greg KH
2004-08-03 23:04 ` Luis Miguel García Mancebo
2004-08-04 20:32 ` Michael Guterl
2004-08-05 1:20 ` [linux-usb-devel] " David Brownell
2004-08-05 3:57 ` Michael Guterl
2004-08-05 15:34 ` David Brownell
2004-08-05 17:05 ` Michael Guterl
2004-08-07 17:51 ` David Brownell
2004-08-07 22:01 ` Wes Janzen [this message]
2004-08-08 3:19 ` Michael Guterl
2004-08-08 4:20 ` Alan Stern
2004-08-08 13:29 ` Michael Guterl
2004-08-10 17:16 ` Michael Guterl
2004-08-10 18:54 ` Alan Stern
2004-08-10 19:41 ` Michael Guterl
2004-08-05 18:08 ` Kevin O'Shea
2004-08-05 18:50 ` Michael Guterl
2004-08-06 14:23 ` Alan Stern
2004-08-05 3:59 ` Michael Guterl
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=41155138.4090707@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=ktech@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mguterl@gmail.com \
/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