Ir Keyboard Drivers - Alpha Release

[web-angel]

Hi !

Test on a C860 with SK6688 wireless keyboard :

It works with anything driver but :

When typing a key the caractere still be tiped until I press another key ...

So :

aaaaaaaaaaaaaaaaaaaaaaaaaaazzzzzzzzzzzzzzzzzzzzzzzeeeeeeeeeeeeerrrrrrrrrr

I think you can understand me ;-)

[kopsis]

When typing a key the caractere still be tiped until I press another key ...

So :

aaaaaaaaaaaaaaaaaaaaaaaaaaazzzzzzzzzzzzzzzzzzzzzzzeeeeeeeeeeeeerrrrrrrrrr

I think you can understand me ;-)
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I do understand the "stuck key" problem you describe. It is caused by the keyboard encoding keystrokes in a way that none of the existing drivers understand. You would need a driver specifically for the SK6688. Unfortunately I do not have the technical information needed to create that driver.

If you can follow [a href=\"http://kopsisengineering.com/kopsis/ZkbddAddingKeyboards]these instructions[/url] and send me the resulting information, I might be able to add an SK6688 driver to the next release (though it may take a few releases to get all the bugs out).

Alternatively, if anyone wants to send me an SK6688, I can easily learn how it works and get a working driver in the next release

[web-angel]

I'have try to have scancode of the keyboard but I have a strange probleme.
A complete press up and down sequence give me about 20 scancode and never the same sequence with the same key ! Thats so funny because when I use a normal driver the correct key is pressed ! Normaly I thing that the scancode of a key can't change right ? So correct me when I have made anything wrong but I don't understand ...

[suzao]

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.

[cal]

Will this run on the new version of pdaxrom yet?

[lindenle]

What model of pocketop keyboards work?

[sds]

The zkbdd driver seems to have stopped working for me on Belkin f8u1500t beginning with 1.1.0. Beta1.
This is both with the zkbdd ipk in the official feed and the one from Kopsis (both are presumably compiled from the same source).

The uinput module gets successfully loaded (keybdev should be in the kernel) and the driver starts successfully. No /dev/misc/uinput device gets created, but /dev/uinput exists. Interestingly, using the -d switch I can see the scancodes are being registered, but no actual symbols appear on the screen. This happens both in console and in aterm/X under the root account.

Is someone using successfully an IR keyboard with a version equal to, or newer, than Beta1?

[kopsis]

The uinput module gets successfully loaded (keybdev should be in the kernel) and the driver starts successfully. No /dev/misc/uinput device gets created, but /dev/uinput exists. Interestingly, using the -d switch I can see the scancodes are being registered, but no actual symbols appear on the screen. This happens both in console and in aterm/X under the root account.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=117219\"][{POST_SNAPBACK}][/a][/div]

The only suggestion I can offer at the moment is try symlinking /dev/misk/uinput to the existing /dev/uinput and see if that helps. It's been a while since I've been able to look at any of this and I'm not sure when I'll be able to revisit it. The combination of a company VPN that needs proprietary Windows software (i.e. a laptop) to access and a smartphone that can handle all the Z's old PIM duties has left my poor old Z collecting dust for a few months now (and with it my Z devel projects). I hate it when I have so many projects all competing for so little free time

BTW - getting the scancodes in is easy ... that's just reading from a com port so I'm not surprised it still works. Getting the resulting keystrokes into the input queue is the hard part. That's where uinput comes in so clearly that's where the breakage is.

[ltrm]

I have a Belkin working with 1.1.0 Beta 1 on a C860.

I hope I'm not stating the obvious here but unless I run

# modprobe keybdev
# modprobe uinput

it doesn't work and complains with uinput no such file or directory errror.

Hope that helps.

ltrm

[mr_clark]

Found somebody selling a F8U1500 (NOT T) cheap. From reading this discussion it sounds like the drivers don't work 100% for this specific keyboard yet. Is this correct? I have a SL-C1000.

[clofland]

Is someone using successfully an IR keyboard with a version equal to, or newer, than Beta1?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=117219\"][{POST_SNAPBACK}][/a][/div]

Just to add to the assurances. I have a f8u1500t and it works fine on my 760 with Beta1.

[sds]

In the meantime I reflashed to 1.1.0Beta2 and I can indeed confirm that both Targus PA 870U V3 and Belkin  f8u1500t work. The keymaps seem slightly off (can't type some chars like "." etc.), but will look later into this.

[byau]

Hey there-

Zaurus: c860 running pdaxrom 1.1.0beta-1
Keyboard: micro-innovations universal wireless keyboard (design by Pocketop).  
Installation:
ipkg install zkbdd (it was in the feed! woo!)
modprobe keybdev
modprobe uinput

Using the pocketop driver.  Here are the few problems:

Problem #1: sticky keys
Problem #2: cannot type the ^ which is [punct][6]

In the test mode [punct][6] is registers and I remember reading in the thread about key mappings so I'm sure this is fixable.

Problem #3: After some time the keymapping goes a bit strange/nuts.  Including both IR keyboard and clamshell keyboard.  I think it is after a certain set of keystrokes and I'm guessing it is with one of the "special" keys (caps lock, shift, ctrl, punct, cmd, num, etc..) at which point I need to reboot the zaurus

Overall:  The stickey keys are mostly a nuisance when typing in passwords.  Rebooting is a bit of a nuisance too.  But other than that works great.   Thanks!

Also as far as starting and killing, i basically use these aliases in my .bashrc file and it works for me.  Shouldn't be any implications of running the modprobes repeatedly should you be typing the "keyon" command repeatedly


alias keyon='modprobe keybdev; modprobe uinput; zkbdd -t pocketop &'
alias keyoff='killall zkbdd'


Thanks again

[darmou]

Are there any keyboard drivers for beta4 and the 2.6 kernel?

darmou

[geek_riot]

Does anyone know of a new source for the kernal-modules-input from Kopsis?  His feed is down.