From: Chase Douglas <chase.douglas@canonical.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] input: ALPS - Add signature for HP Pavilion dm3 laptops
Date: Wed, 21 Apr 2010 08:15:17 -0400 [thread overview]
Message-ID: <p2r40ec3ea41004210515geb17ed8du24ff7d1eb4cc2214@mail.gmail.com> (raw)
In-Reply-To: <20100421041029.GA9482@core.coreip.homeip.net>
On Wed, Apr 21, 2010 at 12:10 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Tue, Apr 20, 2010 at 11:47:20PM -0400, Chase Douglas wrote:
>> On Tue, Apr 20, 2010 at 9:01 AM, Chase Douglas
>> <chase.douglas@canonical.com> wrote:
>> > On Tue, Apr 20, 2010 at 12:29 AM, Dmitry Torokhov
>> > <dmitry.torokhov@gmail.com> wrote:
>> >> That means that our standard magic knock did not work. It seems that
>> >> newer version of ALPS are using a different "magic knock" sequence for
>> >> them.
>> >
>> > How can we find out what the new knock sequence is?
>>
>
> One way would be to run the $OTHER_OS with proper driver inside a VM and
> pass-through all commands from that OS to real PS/2 hardware recodring
> the sequence in process.
Do you know of any documentation on how to do this? I've tried various
google searches, but I'm having difficulty finding information on
sniffing the ps/2 protocol through a vm.
Thanks
-- Chase
next prev parent reply other threads:[~2010-04-21 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 17:51 [PATCH] input: ALPS - Add signature for HP Pavilion dm3 laptops Chase Douglas
2010-03-27 19:11 ` Dmitry Torokhov
2010-04-19 20:36 ` Chase Douglas
2010-04-20 7:29 ` Dmitry Torokhov
2010-04-20 13:01 ` Chase Douglas
2010-04-21 3:47 ` Chase Douglas
2010-04-21 4:10 ` Dmitry Torokhov
2010-04-21 12:15 ` Chase Douglas [this message]
2010-04-21 19:56 ` Dmitry Torokhov
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=p2r40ec3ea41004210515geb17ed8du24ff7d1eb4cc2214@mail.gmail.com \
--to=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).