[oe] fso-console-image problems
Mr Dash Four
mr.dash.four at googlemail.com
Sun Dec 4 13:39:01 CET 2011
> 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!
More information about the Openembedded-devel