From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Chandler Paul <cpaul@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Greg KH <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Joe Perches <joe@perches.com>,
Jiri Slaby <jslaby@suse.com>,
Vishnu Patekar <vishnupatekar0510@gmail.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-api@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [RFC] ps2emu - PS/2 emulation module
Date: Tue, 21 Jul 2015 13:48:02 -0700 [thread overview]
Message-ID: <20150721204802.GE39076@dtor-ws> (raw)
In-Reply-To: <1437505634-8633-1-git-send-email-cpaul@redhat.com>
On Tue, Jul 21, 2015 at 03:07:13PM -0400, Stephen Chandler Paul wrote:
>
> Right now we make use of this module with the ps2emu userland tools[2] that I've
> wrote recently. Recording of PS/2 devices is done by enabling the debugging
> output from i8042, triggering a rescan of the PS/2 ports, and doing some clever
> trimming of data to remove anything that goes across the i8042 chip that isn't
> relevant to the PS/2 protocol. The replay application is pretty simple, and just
There is also serio_raw module that might be easier to use for recording
raw AUX data.
Thanks.
--
Dmitry
prev parent reply other threads:[~2015-07-21 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 19:07 [RFC] ps2emu - PS/2 emulation module Stephen Chandler Paul
2015-07-21 19:07 ` Stephen Chandler Paul
2015-07-21 19:07 ` [RFC] Input: Add ps2emu module Stephen Chandler Paul
2015-07-21 19:15 ` Greg KH
2015-07-21 19:47 ` [RFC 1/1 v2] " Stephen Chandler Paul
2015-07-21 19:57 ` Greg KH
2015-07-21 20:46 ` Dmitry Torokhov
2015-07-21 21:42 ` Stephen Chandler Paul
2015-07-21 22:13 ` Dmitry Torokhov
2015-07-21 19:16 ` [RFC] " Greg KH
2015-07-21 20:48 ` Dmitry Torokhov [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=20150721204802.GE39076@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benjamin.tissoires@redhat.com \
--cc=cpaul@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=sebott@linux.vnet.ibm.com \
--cc=vishnupatekar0510@gmail.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.