Author Topic: Ir Keyboard Drivers - Alpha Release (Read 52336 times)

kopsis · « **Reply #45 on:** October 21, 2005, 07:50:45 am »

Thanks g33k! I knew moving the drivers from compiled-in code to editable scripts was a good idea

As for modifiers, only the shift keys get special treatment -- the others (CTRL, ALT, etc.) are passed through to the Z unmodified. When shift is down it causes lookups to go to "map_shift" instead of "map_normal". If there's a value there, it's passed on as is and the shift keypress itself is dropped. If the value is null, a second lookup from "map_normal" is done and that code is sent along with the shift key press/release.

I'm a vi user not an Emacs person so I haven't really tried any three+ key combinations. If things like CTRL+ALT+key or SHIFT+CTRL+key are giving you problems, let me know (that will required diving into the driver core to debug).

clofland · « **Reply #46 on:** November 09, 2005, 08:44:27 pm »

Two questions:

1. Status? Are these working reliably on RC12 now?

2. Is it just me, or has the Pocketop web site's "ordering" section been down for a long time now? Any suggestions on where to get a Pocketop IR keyboard? Or suggestions on other keyboards that you think are better, cheaper or more available that also works well with pdaXrom?

Thanks.

kopsis · « **Reply #47 on:** November 10, 2005, 07:42:59 am »

I've been so busy with "real work" that I haven't even had a chance to load up RC12. However, I don't know of any reason why the RC11 versions wouldn't work with RC12. Things are going to be crazy through December then hopefully I'll have a bit of free time to catch up on my projects.

clofland · « **Reply #48 on:** November 10, 2005, 10:29:20 am »

One other question. Pocketop has an "original" keyboard and a CT4700. Does anyone know if there is any difference between them as far as compatibility?

sds · « **Reply #49 on:** November 10, 2005, 12:00:05 pm »

I used to have the original Pocketop gotten new and unopened from eBay but I am using a Belkin f8u1500t now.

The belkin_f8u1500t driver works the same under RC12 as under RC11.
The "original" Pocketop keyboard is the one tested for pdaXrom, I don't know about the other.

Pocketop keyboards are the highest build and visual quality, most compact and with best tactile feedback.
However, they are too cramped and small for long typing sessions and the location of some important for programming keys is counterintuitive.

In short, if you will type mostly text docs/emails up to 1-2 hours a session then get a Pocketop.
For longer typing and/or programming/shell work get a Belkin or a similar bigger keyboard.

Many thanks to Dave for his nice work.

clofland · « **Reply #50 on:** November 10, 2005, 02:10:21 pm »

Quote

In short, if you will type mostly text docs/emails up to 1-2 hours a session then get a Pocketop.
For longer typing and/or programming/shell work get a Belkin or a similar bigger keyboard.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=103142\"][{POST_SNAPBACK}][/a][/div]

Thanks for the review! That is just what I needed. Honestly, what I really want is to plug in a full size keyboard, but I'm not sure if I want to upgrade to a C3100 just yet or not.

Sounds like the Belkin is more what I need.

Someone is selling a whole bunch of them on Ebay now for $20 plus $8 shipping. (Though it doesn't look like he ships outside of the US/CAN). Just do a search for F8U1500 on Ebay and you will see them.

Hopefull the differnences between the T and non-T version can be worked out in the drivers.

zaurus_usa · « **Reply #51 on:** November 14, 2005, 04:19:22 pm »

Hi, I'm using SL-C860 & RC12.
I tried your driver with my Pocketop keyboard. Thank you for your great work ! It
encourages me to migrate to pdaXrom. Below are several problems that I
noticed. Sorry if similar problems have already been posted.

(1) With modifier key (Shift/Ctrl) pressed down, press & release any key (say,
'a'), and it works fine. but once you press 'a' again, it repeats forever until
you press a different key. I'm Emacs user so it is a little annoying .

(2) '^' cannot be input. I can type '6' but Punct modifier doesn't work.

(3) Caps Lock doesn't work by itself; I need to press Shift and Caps Lock down
at the same time to make it work. (Is it as intended?)

Thanks.

jandr · « **Reply #52 on:** November 15, 2005, 12:07:37 am »

For what it's worth, my Belkin F8U1500-E works great with the 1500t driver
under rc10 on my 760... I assume it'll be just as good with rc12. Thanks a bunch!

zaurus_usa · « **Reply #53 on:** November 15, 2005, 01:17:01 am »

Hi,
The problem mentioned above might be due to my operation problem, but anyway, being interested, I tried to download the source code to see whether I can do anything by myself. However, the link to the source code at http://kopsisengineering.com/kopsis/ZkbddDownload is invalid. Can you please fix it or tell me where it is available?

kopsis · « **Reply #54 on:** November 15, 2005, 08:40:35 am »

Source code download link is fixed.

suzao · « **Reply #55 on:** November 15, 2005, 12:32:51 pm »

I am attempting to get zkbdd to work on my c3100. I have installed all 3 ipks from http://kopsisengineering.com/rc11/Zaurus-C1000-C3100/feed

I modprobe uinput and shows up in lsmod. Then when I start zkbdd from a terminal the following error comes up:
failed to open uinput device: No such file or directory
init uinput failed

I eventually will use a ThinkOutside ir keyboard, but first I just need to get zkbdd to work. This error comes up if I try the default keyboard, or with zkbdd -t palm_wireless, zkbdd -t targus, etc. All the lua files are confirmed to reside in /usr/share/zkbdd/drivers and are readable by root (who I am logged in as)

Does somebody know what file or directory it might be referring to?

I have a c3100 running pdaxrom rc12.

kopsis · « **Reply #56 on:** November 16, 2005, 12:00:57 pm »

Quote

I modprobe uinput and shows up in lsmod. Then when I start zkbdd from a terminal the following error comes up:
failed to open uinput device: No such file or directory
init uinput failed
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

The solution is a [a href=\"https://www.oesf.org/forums/index.php?showtopic=15484&view=findpost&p=99596]few posts back[/url].

adf · « **Reply #57 on:** November 16, 2005, 01:29:13 pm »

My 6k on rc12 (with a hot plugging usb mouse) is once again a tiny laptop. The drivers are excellent! Thanks,
ADF

clofland · « **Reply #58 on:** November 21, 2005, 12:11:39 pm »

Just got a Belkin f8u1500t (Ebay). Very cool.

First annoyance though, if I hit CAPS Lock and then hit the backspace key, the Z suspends. I am guessing this has something to do with the fact that the backspace key has a sub-function of "off", but I thought that should realte to the Fn key and not the Caps Lock?

Anyway, I guess I can muck with the keymapping myself now, so I'll go take a look see.

Again, thanks Kopsis, this is awesome!

EDIT: Is there a way to map to the MAIL, HOME and MENU keys? I find the ACTIVITY and CONTACTS key in the list, but I can't find the other three.

Thanks.

Katsuyoshi Nakanishi · « **Reply #59 on:** November 22, 2005, 04:21:30 am »

Hi zaurus_usa, Kopsis,

I had the same problem as (1) mentioned by zaurus_usa, and looked at the code.
It seems last_keyup wasn't cleared and it was filtering keyup signal when the same key was *actually* repeated. I changed
/usr/share/zkbdd/drivers/pocketop.lua as follows (from line 146):

from:

Code: [Select]

    -- filter final keyup signal
    if key_down == 0 then
  if key == last_keyup then
      last_keyup = 0
      return 0, key_down
  end
  last_keyup = key;
    end

to:

Code: [Select]

    -- filter final keyup signal
    if key_down == 0 then
  if key == last_keyup then
      last_keyup = 0
      return 0, key_down
  end
  last_keyup = key;
    elseif key == last_keyup
  last_keyup = 0;
    end

and now it seems to be working correctly.
---
Katsu

News:

Author Topic: Ir Keyboard Drivers - Alpha Release (Read 52336 times)