All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: bcrl@redhat.com, satch@fluent-access.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: FYI  PS/2 Mouse problems -- userland issue
Date: Tue, 21 Aug 2001 19:40:27 GMT	[thread overview]
Message-ID: <200108211940.TAA184696@vlet.cwi.nl> (raw)

    From: Ben LaHaise <bcrl@redhat.com>

    On Tue, 21 Aug 2001, Stephen Satchell wrote:

    > This MAY be a kernel issue depending on where I locate the mouse
    > initialization code.  If it is in the kernel, then there will need
    > to be a patch to allow the mouse to be re-initialized into the mode
    > everyone expects.

[Funny - we just discussed this last week.]

    The kernel has nothing to do with reinitializing the mouse: X has to do
    that.

[Indeed. Or gpm.]

     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.

Have you written the patch already?
There are interesting difficulties here.

Andries

             reply	other threads:[~2001-08-21 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 19:40 Andries.Brouwer [this message]
2001-08-21 20:22 ` FYI PS/2 Mouse problems -- userland issue Ben LaHaise
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 22:35 Andries.Brouwer
2001-08-21 22:41 ` Ben LaHaise
2001-08-22 18:09 ` Gunther Mayer
     [not found] <mailman.998417940.18388.linux-kernel2news@redhat.com>
2001-08-21 18:59 ` Pete Zaitcev
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=200108211940.TAA184696@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satch@fluent-access.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 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.