All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: bcrl@redhat.com
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: FYI  PS/2 Mouse problems -- userland issue
Date: Tue, 21 Aug 2001 14:59:08 -0400	[thread overview]
Message-ID: <200108211859.f7LIx8A18707@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.998417940.18388.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.998417940.18388.linux-kernel2news@redhat.com>

> [...] it needs a few improvements during 2.5: I plan to submit a
> patch that replaces much of the existing pc keyboard/mouse code with state
> machine driven code that doesn't block interrupts out for long periods of
> time, as well as fixing a few of the lockup issues the current driver has.
> 
> 		-ben

Interesting. BTW, there is a request to introduce the mouse
into the Input/HID framework in the way PS/2 keyboard is now.
It does not overlap too much with a fix to hardware access,
but it may help to remove the multitude of broken code from
userland and direct it at your super-duper-state-machine code.

 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=50921

-- Pete

       reply	other threads:[~2001-08-21 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.998417940.18388.linux-kernel2news@redhat.com>
2001-08-21 18:59 ` Pete Zaitcev [this message]
2001-08-21 22:35 FYI PS/2 Mouse problems -- userland issue Andries.Brouwer
2001-08-21 22:41 ` Ben LaHaise
2001-08-22 18:09 ` Gunther Mayer
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 19:40 Andries.Brouwer
2001-08-21 20:22 ` Ben LaHaise
2001-08-21 18:07 Stephen Satchell
2001-08-21 18:17 ` Ben LaHaise
2001-08-21 18:28   ` James Simmons
2001-08-21 18:35     ` Ben LaHaise
2001-08-21 20:30       ` James Simmons
2001-08-21 20:29 ` Kurt Garloff

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=200108211859.f7LIx8A18707@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.