All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [patch commit request] kdrive xserver:	support	for	key	codes 128-255
Date: Sat, 09 Feb 2008 07:00:34 -0600	[thread overview]
Message-ID: <47ADA3F2.1000500@gmail.com> (raw)
In-Reply-To: <1202075839.17746.11.camel@utx.utx.cz>

On 02/03/2008 03:57 PM, Stanislav Brabec wrote:
> Junqian Gordon Xu wrote:
>> On 01/30/2008 06:13 AM, Stanislav Brabec wrote:
>>>> Paul Sokolovsky wrote:
>>>> Can you please elaborate what the application of this patch would mean
>>>> for OE (besides fixing support for one specific obscure peripheral)? 
>> I guess I probably would be yelled at for not raising this before 
>> committing your patch.
>>
>> Is this patch specific to Zaurus clamshells, akita/spitz/c7x0? In other 
>> words, are there any other devices benifiting from the extended keycode. 
>>   I vaguely remember Dmitry asked about extended keycode for tosa, but 
>> I'm not sure he's talking about the same thing.
> 
> No. It adds support for key codes 128-255 in general.

I understand this patch is general. But could you educate me that except 
for the Z clamshells, what's the use case for other devices? I guess my 
question is more in line with Paul's challenge. Is this patch just a 
why-not for other devices or something might be helpful?

Regards
Gordon




  parent reply	other threads:[~2008-02-09 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 18:19 [patch commit request] kdrive xserver: support for key codes 128-255 Stanislav Brabec
2008-01-30  1:38 ` Junqian Gordon Xu
2008-01-30 10:45 ` Paul Sokolovsky
2008-01-30 12:13   ` Stanislav Brabec
2008-02-01  8:02     ` Junqian Gordon Xu
2008-02-03 21:57       ` Stanislav Brabec
2008-02-04  1:12         ` Dmitry Baryshkov
2008-02-04 11:05           ` Stanislav Brabec
2008-02-09 13:00         ` Junqian Gordon Xu [this message]
2008-02-09 13:40           ` Paul Sokolovsky
2008-02-10 21:33           ` Stanislav Brabec
2008-02-01  7:03 ` Junqian Gordon Xu

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=47ADA3F2.1000500@gmail.com \
    --to=xjqian@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.