mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: viking <viking@flying-brick.caverock.net.nz>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: USB mouse hiccups
Date: Mon, 21 Mar 2005 13:36:12 +1200	[thread overview]
Message-ID: <20050321013612.GA7168@flying-brick.caverock.net.nz> (raw)
In-Reply-To: <20050320164129.44d3a065.akpm@osdl.org>

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?

Yeesh. You ARE keen, aren't you. I'll attempt to do so over the next day or
so. Thanks.

-- 
 /|   _,.:*^*:.,   |\  Cheers from the Viking family, including Pippin, our cat
| |_/'  viking@ `\_| |
|    flying-brick    | $FunnyMail   : What do you mean, I've lost the plot?
 \_.caverock.net.nz_/     5.40      : I planted them carrots right here!!

  reply	other threads:[~2005-03-21  1:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 22:09 USB mouse hiccups (was RFD: Kernel release numbering) viking
2005-03-21  0:41 ` Andrew Morton
2005-03-21  1:36   ` viking [this message]
2005-03-21  7:26   ` viking
2005-03-21  7:32     ` Andrew Morton

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=20050321013612.GA7168@flying-brick.caverock.net.nz \
    --to=viking@flying-brick.caverock.net.nz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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®