From: Andrew Morton <akpm@osdl.org>
To: viking <viking@flying-brick.caverock.net.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB mouse hiccups (was RFD: Kernel release numbering)
Date: Sun, 20 Mar 2005 23:32:27 -0800 [thread overview]
Message-ID: <20050320233227.2c7b8013.akpm@osdl.org> (raw)
In-Reply-To: <20050321072601.GA31826@flying-brick.caverock.net.nz>
viking <viking@flying-brick.caverock.net.nz> wrote:
>
> On Sun, Mar 20, 2005 at 04:41:29PM -0800, Andrew Morton wrote:
> > viking <viking@flying-brick.caverock.net.nz> wrote:
> > >
> > > I did note something strange. I'm running 2.6.11.2 at this moment, when I
> > > tried 2.6.11.3, my USB Microsoft Wireless Optical Mouse stopped moving
> > > from left to right, and would only move up and down if I physically moved
> > > the mouse from left to right. I didn't see anything in the patches that
> > > touched anything in the event handling, so frankly I'm puzzled.
> > > Any clues as to where I need to look? I've seen this problem before, but
> > > don't know what causes it, nor how I fixed it at the time.
> > > Also, how do I get that patch that enables the tiltwheel (left-right
> > > events)?
> >
> > Could you please test 2.6.12-rc1?
>
> Got it compiled this evening. How many days do you want me to run it for? A
> week?
Well it should take about seven seconds to work out if the mouse movement
is still broken?
> Can I test out the suspend-to-disk on this release too?
Please do.
prev parent reply other threads:[~2005-03-21 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 22:09 viking
2005-03-21 0:41 ` Andrew Morton
2005-03-21 1:36 ` USB mouse hiccups viking
2005-03-21 7:26 ` USB mouse hiccups (was RFD: Kernel release numbering) viking
2005-03-21 7:32 ` Andrew Morton [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=20050320233227.2c7b8013.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viking@flying-brick.caverock.net.nz \
/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
all inboxes | Powered by JetHome®