From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Horrible mouse performance
Date: Fri, 22 Nov 2002 18:51:49 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805476@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805469@msgid-missing>
>>>>> On Fri, 22 Nov 2002 12:25:38 +1100, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> Hi, When using the linux 2.5.45+IA64patch kernel on an I2000,
Peter> the mouse pointer lags actual mouse movements by a long time,
Peter> making X almost unusable. I haven't configured in the frame
Peter> buffer, if that makes a difference.
There certainly are problems with the input layer in 2.5. So the
keyboard is actually working for you? That's better than it used to
be! ;-) Both mouse and keyboard are connected via PS/2, not via USB, I
assume?
(I don't normally see such problems because I do most of my 2.5 work
remotely, without console access.)
--david
next prev parent reply other threads:[~2002-11-22 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 1:25 [Linux-ia64] Horrible mouse performance Peter Chubb
2002-11-22 18:51 ` David Mosberger [this message]
2002-11-23 7:50 ` Peter Chubb
2002-11-25 17:58 ` David Mosberger
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=marc-linux-ia64-105590709805476@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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