Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: fso-console-image problems
Date: Sun, 04 Dec 2011 12:39:01 +0000	[thread overview]
Message-ID: <4EDB69E5.3050809@googlemail.com> (raw)
In-Reply-To: <4EDA6C03.1040308@googlemail.com>


> Noted, though what I did in the meantime is I logged in via ssh (see 
> below :-) ), called nano, cut-and-paste job from my PC's htcuniversal 
> keymap file, saved this as /etc/keymap-2.6.map (on the phone) and then 
> executed /etc/init.d/keymap - the layout has changed somewhat but it 
> is not what I need, so I am going to see if I could make the 
> corrections I need so that this file matches the htcdream layout exactly.
>
> There are quite a few "non-standard" keys (like "home", "back", two 
> different "alt" keys, one "search" key etc) which I am hoping to 
> capture with this layout config - will search google for the tool to 
> use to see what scan codes they transmit (provided this is how the 
> "keycode" works, that is).
Not having much luck with this at the moment! I dumped the entire 
key-mapping configuration to a separate file using dumpkeys and tried, 
as a test, to reconfigure a non-standard key (called 'menu') to emit the 
letter 'z' when pressed - at least that was the idea.

When I ran "showkeys -s" (to see what was the scan code of that key) I 
noted it as "0xe0 0x5e", so I then did the following: "setkeycodes e05e 
44" (44 in the already-dumped keymap is defined as "keycode 44 = +z +Z 
+z Control_z Control_z Meta_z Meta_Control_z"). After doing that, I 
pressed the "menu" key a couple of times, but nothing happened.

I then tried to remap another "non-standard" key - my "Back" key on the 
actual phone, but again nothing happens (when I press it, it emits '?' 
*regardless* of whether this key is re-defined by me or not). Lastly, I 
tried to do this trick on a "known" key - '1' (scancode 2): no problem, 
it emits the letter 'z' as it should.

I don't know if I am doing this wrong and why it doesn't work with 
"non-standard" keys, maybe the kernel keyboard driver is somehow 
"stopping" these - I have no idea at this point!



      reply	other threads:[~2011-12-04 12:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  1:57 fso-console-image problems Mr Dash Four
2011-12-02 10:20 ` Denis 'GNUtoo' Carikli
2011-12-02 14:08   ` Mr Dash Four
2011-12-02 14:52     ` Martin Jansa
2011-12-02 15:12       ` Mr Dash Four
2011-12-02 15:46         ` Martin Jansa
2011-12-02 16:20           ` Mr Dash Four
2011-12-02 16:25             ` Martin Jansa
2011-12-02 17:27       ` Denis 'GNUtoo' Carikli
2011-12-02 17:42         ` Mr Dash Four
2011-12-02 20:06       ` Mr Dash Four
2011-12-02 22:24         ` Denis 'GNUtoo' Carikli
2011-12-02 23:35           ` Mr Dash Four
2011-12-02 23:50             ` Mr Dash Four
2011-12-03  9:46               ` Denis 'GNUtoo' Carikli
2011-12-03 16:37                 ` Mr Dash Four
2011-12-03 16:52                   ` Martin Jansa
2011-12-03 17:47                     ` Mr Dash Four
2011-12-03 18:03                       ` Martin Jansa
2011-12-03 18:35                         ` Mr Dash Four
2011-12-04 12:39                           ` Mr Dash Four [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=4EDB69E5.3050809@googlemail.com \
    --to=mr.dash.four@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox