> > Hi > > The FN key on N810 keyboard seems to send (the standard FN) keycode 464 > which is a bit tricky as X doesn't support keycodes over 255 (afaik). > > HAL should be able to remap the keycodes using the EVIOCSKEYCODE with > the ioctl but I get EINVAL on n810 and n800 when I try to use it. On my > PC it works without errors. > > I wonder how's this done in Maemo's Xomap? > > -- > Tuomas > > > _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers

Attached Files:

Tuomas Kulve wrote: > Hi > > The FN key on N810 keyboard seems to send (the standard FN) keycode 464 > which is a bit tricky as X doesn't support keycodes over 255 (afaik). > > HAL should be able to remap the keycodes using the EVIOCSKEYCODE with > the ioctl but I get EINVAL on n810 and n800 when I try to use it. On my > PC it works without errors.

Sorry I can't help, but I wonder if someone can help me with my keyboard problem?

I have a ThinkOutside stowaway bluetooth keyboard and several of the keys are dead, as far as I can tell because evdev ignores their keycodes. Unlike this case, however, the keycodes that get sent are under 255, so it sounds like I should be able to do this HAL/EVIOCSKEYCODE thing to remap them to something else.

Can someone give me some pointers on how to do this? After googling, I think I need to use hal-set-property to set some properties, but after trying to set various keys to "b", it doesn't seem to be having any effect. I don't know if I'm allowed to simply append "input.keymap" to the list of capabilities, and it will magically make my keyboard capable of that?

Tuomas Kulve wrote: > Matthew Exon wrote: > >> I have a ThinkOutside stowaway bluetooth keyboard and several of the >> keys are dead, as far as I can tell because evdev ignores their >> keycodes. Unlike this case, however, the keycodes that get sent are >> under 255, so it sounds like I should be able to do this >> HAL/EVIOCSKEYCODE thing to remap them to something else. > > The EVIOCSKEYCODE is not limited to 255. I would guess that you cannot > map them unless they are sent in the first place. > > You can use the attached evtest to see what the event device is sending > below X and you can use the attached xev to see how X sees them.