Show Posts
1
Zaurus - pdaXrom / Ir Keyboard Drivers - Alpha Release
« on: December 01, 2005, 01:01:38 am »
I guess I am one of the few lucky ones, my Belkin keyboard is a model F8U1500 no "T" on the end. I have confirmed that the protocol it uses is moderately different from the T model. The map is the same but the noT model uses 2 bytes for each key down and key up. For example using zkbdd -d -t test9600 settings pressing the "a" key outputs 66 65 then letting up on the key produces 193 193
All the keys are similar in that that the key group is first then the key map#, and on key another key group is repeated twice.
I would like to modify the belkin_f8u1500t.lua file to work with the noT model. But first I need a little clarification on exactly how zkbdd uses the lua files. Looking at the source I am guessing that zkbdd calls on the function do_scancode (s) from the lua file. Is this function called for each byte or only once per keypress/release event?
Also since the extra guard bytes are not present (like in the withT model) I need details so I can get the logic correct. I have posted the map file I made for each key on the F8U1500 keyboard, just know that on the keyup event the code given in repeated each time.
Thanks for any input.
All the keys are similar in that that the key group is first then the key map#, and on key another key group is repeated twice.
I would like to modify the belkin_f8u1500t.lua file to work with the noT model. But first I need a little clarification on exactly how zkbdd uses the lua files. Looking at the source I am guessing that zkbdd calls on the function do_scancode (s) from the lua file. Is this function called for each byte or only once per keypress/release event?
Also since the extra guard bytes are not present (like in the withT model) I need details so I can get the logic correct. I have posted the map file I made for each key on the F8U1500 keyboard, just know that on the keyup event the code given in repeated each time.
Thanks for any input.