public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Micah Parrish <micah.parrish@hp.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] Input: tell mousedev to handle remote console virtual mice using absolute coordinates
Date: Wed, 9 Jan 2008 09:26:39 -0700	[thread overview]
Message-ID: <20080109162639.GA30033@ldl.fc.hp.com> (raw)
In-Reply-To: <1198188164.7371.40.camel@strongbad>

Hi Dmitry,

* Micah Parrish <micah.parrish@hp.com>:
> Devices like the HP Integrated Remote Console Virtual Mouse, which are
> standard equipment on all Proliant and Integrity servers, produce
> absolute coordinates instead of relative coordinates.  This is done to
> synchronize the position of the mouse cursor on the client desktop
> with the mouse cursor position on the server.  Mousedev is not
> designed to pass those absolute events directly to X, but it can
> translate them into relative movements.  It currently does this for
> tablet like devices and touchpads.  This patch merely tells it to also
> include a device with ABS_X, ABS_Y, and mouse buttons in its list of
> devices to process input for.
> 
> This patch enables the mouse pointer to move when using the remote
> console.  Without this patch, the cursor will not move.

We're looking to get this patch accepted into a distro, which is
of course easier if it is first accepted upstream.

Is there anything we can do to help explain this patch further to
enable acceptance?

Thanks.

/ac


      reply	other threads:[~2008-01-09 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 22:02 [PATCH RFC] Input: tell mousedev to handle remote console virtual mice using absolute coordinates Micah Parrish
2008-01-09 16:26 ` Alex Chiang [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=20080109162639.GA30033@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=micah.parrish@hp.com \
    --cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox