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.
OK, you're right, it's somewhere below X: I don't get anything from evtest for my dead keys (I'd tried xev already). But these keys work fine for my desktop machine, so I thought this sounded similar to your problem. Maybe not. Where does evtest come from? Thanks, Mat _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
