From: Mattia Dongili <malattia@linux.it>
To: Gyorgy Jeney <nog.lkml@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthew Garrett <mjg@redhat.com>
Subject: Re: On a sony VAIO Z12C5E: sony-laptop: Unknown event: 0x100 0xa6, etc.
Date: Fri, 26 Nov 2010 07:58:18 +0900 [thread overview]
Message-ID: <20101125225818.GA9301@kamineko.org> (raw)
In-Reply-To: <AANLkTikovTWaR5jODHwmhaNSL8kzGvoXDsmaYCqgM-ra@mail.gmail.com>
On Thu, Nov 25, 2010 at 11:11:26PM +0100, Gyorgy Jeney wrote:
> On 24 November 2010 23:57, Gyorgy Jeney <nog.lkml@gmail.com> wrote:
> > On 24 November 2010 23:30, Mattia Dongili <malattia@linux.it> wrote:
> >> On Wed, Nov 24, 2010 at 07:22:55PM +0100, Gyorgy Jeney wrote:
> >>> make these events "do the right thing".
> >>
> >> yes, it's easy with the information you provided.
> >> The attached patch should get the keys reported on the input subsystem
> >> and show up on the event device (check with evtest) and X (check with
> >> xev).
> >
> > Thanks, I'll install your patch and test this tomorrow.
>
> I patched a 2.6.37-rc3 kernel and it works perfectly for me. I
Thanks
> noticed when applying the patch that there was an 8 line offset. Does
> this mean there is newer version of sony-laptop.c than is available in
> 2.6.37-rc3?
No, it's just that the diff was not against a clean copy but against my
local version that has tiny adjustments that I never submitted.
Matthew,
Shall I reesend the patch with a proper subject or can you take the one
I posted earlier in this thread?
Thanks!
--
mattia
:wq!
next prev parent reply other threads:[~2010-11-25 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 18:22 On a sony VAIO Z12C5E: sony-laptop: Unknown event: 0x100 0xa6, etc Gyorgy Jeney
2010-11-24 22:30 ` Mattia Dongili
2010-11-24 22:57 ` Gyorgy Jeney
2010-11-25 22:11 ` Gyorgy Jeney
2010-11-25 22:58 ` Mattia Dongili [this message]
2010-11-27 8:36 ` 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=20101125225818.GA9301@kamineko.org \
--to=malattia@linux.it \
--cc=dmitry.torokhov@gmail.com \
--cc=mjg@redhat.com \
--cc=nog.lkml@gmail.com \
--cc=platform-driver-x86@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.