Help - Search - Members - Calendar
Full Version: Silkscreen Does Not Work Under Pdaxrom On Sl-c1000
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
Shmigol
Silkscreen doesn't work under pdaXrom on SL-C1000. Maybe need change keycode in /etc/X11/kb/akita.xmodmap.
Akitabara
Same here. Can't change keycodes in xmodmap file because tapping the silkscreen icons doesn't trigger a keypress (xev doesn't report any event).
Vitel
Hi guys,

Yeah, it's known problem - corgi silkscreen patch is not applied for akita models by default. I've fixed it recently.

This is the list of differences between my patch and default patch for corgi:

1. 12 pixel in width bar is added between silkscreen buttons and display. There is no reaction on clicking on it. The aim of this feature is to avoid undesirable key clicking when you are scrolling in the landscape mode for example.

2. Added feature to allow clicking on one key two times in a row. It's locked in corgi patch, but I think it's useful. For example, we can bind one key to the following script to run/terminate virtual keyboard:
#!/bin/bash
if [ -z `ps aux | pgrep xvkbd` ]
then xvkbd -no-keypad
else killall xvkbd
fi

3. Key codes are changed to 121-125. The old keymap is uncomfortable because one of old key codes is equal to Shift_R button key code.

There are links to download
for Linux 2.4:
http://zavrik.ru/upload/xfree/beta3/fbdev.c.diff
http://zavrik.ru/upload/xfree/beta3/tslib.c.diff
http://zavrik.ru/upload/xfree/beta3/xfree_4.4.0_armv5tel.ipk
for Linux 2.6
http://zavrik.ru/upload/xfree/beta4/fbdev.c.diff
http://zavrik.ru/upload/xfree/beta4/tslib.c.diff
http://zavrik.ru/upload/xfree/beta4/xfree_4.4.0_armv5tel.ipk

You just need to remove old xfree package and install the new one. It's working for me, I hope It'll help you too smile.gif

WBR,
Vitel
zi99y
Wow, excellent, has desertrat seen this he was asking about it too!

So is it safe to use on a C3200? I never remember my dog name...

thanks for looking into this
zi99y
WARNING: backup your old X11 config before you remove/reinstall this: I recommend taking a copy of everything in /etc/X11 and /usrX11R6/bin/startx script that may have been modified. Fortunately I thought of this first smile.gif

Anyway I've tried it on my 3200 and it doesn't seem to work, when I use xev it doesn't show up keycodes, but, it does seem to react differently to the rest of the screen - I only had a short time to test before leaving for work so I will look into it further another time.

Vitel: Can you give us some detail on what has been patched as it may just need a little tweak for other models.

Ta
kkazakov13
I tested it, it's safe. Everything works as usual, now xev catches the silkscreen smile.gif


thanks!
zi99y
I've been having a play and they do actually work! I am getting
responses from keycodes 121 - 125. The problem it seems is that if I
click key 125 (home) it acts as ctrl and locks on until you click
key 121 or 122 to remove the lock. This was very deceptive at first
because the keyboard went berzerk since every keypress was using the
ctrl modifier.

There's nothing in my xmodmap definition file or
/etc/sysconfig/keyboard/kernel.map that shows anything causing this.
Anyone else found the same issue or is it just my over-customised setup?

smile.gif
desertrat
QUOTE(zi99y @ Dec 7 2006, 08:12 AM)
Wow, excellent, has desertrat seen this he was asking about it too!

Yeah I saw this earlier and downloaded the ipk. But I haven't been brave enough to try it yet, because the last time I upgraded X it hosed my Xfce setup smile.gif
http://www.oesf.org/forums/index.php?showt...ndpost&p=104699

QUOTE
The problem it seems is that if I click key 125 (home) it acts as ctrl and locks on until you click
key 121 or 122 to remove the lock.

Could it be in any way related to this nasty problem?
http://www.oesf.org/forums/index.php?showt...ndpost&p=140368
Meanie
QUOTE(desertrat @ Dec 8 2006, 07:34 AM)
QUOTE(zi99y @ Dec 7 2006, 08:12 AM)
Wow, excellent, has desertrat seen this he was asking about it too!

Yeah I saw this earlier and downloaded the ipk. But I haven't been brave enough to try it yet, because the last time I upgraded X it hosed my Xfce setup smile.gif
http://www.oesf.org/forums/index.php?showt...ndpost&p=104699

QUOTE
The problem it seems is that if I click key 125 (home) it acts as ctrl and locks on until you click
key 121 or 122 to remove the lock.

Could it be in any way related to this nasty problem?
http://www.oesf.org/forums/index.php?showt...ndpost&p=140368
*



if you are scared, all you need to do is extract the files from the ipk and just replace Xfbdev under /usr/X11R6/bin
Akitabara
QUOTE(desertrat)
QUOTE(zi99y)
The problem it seems is that if I click key 125 (home) it acts as ctrl and locks on until you click
key 121 or 122 to remove the lock.

Could it be in any way related to this nasty problem?
http://www.oesf.org/forums/index.php?showt...ndpost&p=140368
*



I have the same issue. I've been tinkering a bit and I think it has something to do with Fluxbox too.

When I tap any of the silkscreen icons, the keyboard stops responding. It just locks - xev doesn't report keypresses, not even xvkbd works. For some reason the bottom row of app buttons and the Menu button still work, though.

Let's say I have this on ~/.fluxbox/keys:
CODE
None XF86Launch0    : exec aterm
None XF86Launch1    : exec aterm
None XF86Launch2    : exec aterm
None XF86Launch3    : exec aterm
None XF86Launch4    : exec aterm

I have aterm assigned to all silkscreen keys. When I tap e.g. the Calendar icon, aterm opens, but I can't type anything because the keyboard has been locked. Tapping any other icon opens the assigned program, but the keyboard stays locked. Only exiting X or restarting Fluxbox brings the keyboard back.

Now remove one of those lines from ~/.fluxbox/keys, e.g. the one for the Mail silkscreen button:
CODE
None XF86Launch3    : exec aterm

Launch Fluxbox again. Nothing happens when tapping the Mail icon (as expected) but this time the keyboard doesn't lock. Note that the rest of the icons still open aterm and lock the keyboard, but only until you tap the Mail icon: it does nothing (because it has no action assigned) but the keyboard will unlock.

So this is the workaround I'm using: I chose the Calendar icon to unlock the keyboard, so I left the line regarding XF86Launch1 out of my ~/.fluxbox/keys file. After tapping any other icon I have to tap the Calendar one to be able to use the keyboard.
No big deal for me because all I wanted was a way to swap mouse buttons and open the Fluxbox rootmenu in PDA mode, but IMHO this issue needs a fix.
pelrun
Sounds suspiciously like a key release problem, and after looking at the code I'm certain of it.

The code isn't doing a simple key-down/key-up like I would have expected, it's trying something a bit more complex with timing involved, probably to allow a silkscreen key to be held down.

Unfortunately there's a bug - it now only releases a silkscreen button if another silkscreen button is pressed (oops.) It really should be releasing the key no matter what, unless the same silkscreen key is still being held down.

No guarantees if the following code is any better; it's 4am, I don't have anything set up to actually recompile X here, so this is just a rough stab. I don't even know when/how often tsread is called, especially after the stylus is removed from the screen.

Replace the entire block in tslib.c that begins:

CODE
if (event.y > hack_ts_max_y + 12) {

with
CODE
    if (event.y > hack_ts_max_y + 12)
    {
 int code = 0;
 switch (event.x / (hack_ts_max_x / 5))
 {
     case 0: code = 113; break;
     case 1: code = 114; break;
     case 2: code = 115; break;
     case 3: code = 116; break;
     case 4: code = 117; break;
     default: break;
 }
 time_t currentts = time(NULL);
 if (currentts == lastts) return;
 if (lastcode != code)
 {
     if (lastcode != -1) KdEnqueueKeyboardEvent (lastcode, 0x80);
     KdEnqueueKeyboardEvent (code, 0);
     lastcode = code;
     lastts=currentts;
 }
 return;
    }
    else if (lastcode != -1)
    {
 KdEnqueueKeyboardEvent (lastcode, 0x80);
 lastcode = -1;
    }
Akitabara
Nice! I'd compile it myself, but I don't have t3h skillz yet...
zi99y
I don't really have the means right now either, but when I have the time I intend to setup a cross compile environment (I get mysterious errors compiling natively).

For the time being, leaving the middle button unmapped does seem to work as mentioned above, I just click it after clicking the other buttons to free up the ctrl lock
Vitel
Hi guys,

Sorry for the late reply.

Thanks to all of you, especially to pelrun.
QUOTE(pelrun @ Posted Dec 9 2006 @ 10:11 AM)
Unfortunately there's a bug - it now only releases a silkscreen button if another silkscreen button is pressed (oops.) It really should be releasing the key no matter what, unless the same silkscreen key is still being held down.
I think you are right and this is the thing that exactly locks key pressing.
QUOTE(pelrun @ Posted Dec 9 2006 @ 10:11 AM)
No guarantees if the following code is any better; it's 4am, I don't have anything set up to actually recompile X here, so this is just a rough stab. I don't even know when/how often tsread is called, especially after the stylus is removed from the screen.
I've modified code to provide "simple key-down/key-up". Old key code is no more stored, but timing is still remained to avoid following issue. TsRead function is called many times on every touchscreen clicking and if there is no any delay, then zaurus will have to execute binded action many times (for example, running some program). Therefore zaurus can freeze.
Thus each clicking of silkscreen keys will release pressed key and locking problem should not be reproducible now.

So, the new versions of patch and compiled xfree packages can be downloaded here:

for Linux 2.4:
http://zavrik.ru/upload/xfree/linux_2.4/tslib.c.diff
http://zavrik.ru/upload/xfree/linux_2.4/xf....0_armv5tel.ipk
for Linux 2.6:
http://zavrik.ru/upload/xfree/linux_2.6/tslib.c.diff
http://zavrik.ru/upload/xfree/linux_2.6/xf....0_armv5tel.ipk

I'm awaiting for your replies and hope this will work better.

WBR,
Vitel
zi99y
Many thanks for updating this, I've just extracted Xfbdev as per Meanies note above and replaced the old one and so far silkscreen is working fine without the previous glitch.

Cheers!
daniel3000
QUOTE(Vitel @ Jan 4 2007, 04:08 AM)
So, the new versions of patch and compiled xfree packages can be downloaded here:

for Linux 2.4:
http://zavrik.ru/upload/xfree/linux_2.4/tslib.c.diff
http://zavrik.ru/upload/xfree/linux_2.4/xf....0_armv5tel.ipk
for Linux 2.6:
http://zavrik.ru/upload/xfree/linux_2.6/tslib.c.diff
http://zavrik.ru/upload/xfree/linux_2.6/xf....0_armv5tel.ipk

I'm awaiting for your replies and hope this will work better.

WBR,
Vitel
*



Hi Vitel,

are these files still available anywere?
Your links are dead.

I'd be interesting in testing this!

Thanks a lot
daniel
daniel3000
Well, don't mind. I found it in Meanie's feed.
Where else? smile.gif

Thanks once again, Meanie!

daniel
Vitel
Hi daniel,

zavrik.ru is temporary unavailable, sorry.
It's really nice that you've find an alternative source to download these files, but I think it'd be better to attach them to this topic.

WBR,
Vitel
daniel3000
QUOTE(Vitel @ Feb 13 2007, 12:17 AM)
Hi daniel,

zavrik.ru is temporary unavailable, sorry.
It's really nice that you've find an alternative source to download these files, but I think it'd be better to attach them to this topic.

WBR,
Vitel
*


Well, I had the problem with the Xfbdev file from Meanie's IPK that the Ctrl key was locked active after using the silkscreen buttons.
So I dropped that other Xfbdev again and used the original without silkscreen support.

Is there any way around that problem?

Thanks!
daniel
zi99y
Yes, I've been using silkscreen on my 3200 with Vitel's new Xfbdev file (extracted and copied without installing the whole ipk). The ctrl key locking prob is now fully sorted smile.gif
Meanie
QUOTE(Vitel @ Feb 13 2007, 08:17 AM)
Hi daniel,

zavrik.ru is temporary unavailable, sorry.
It's really nice that you've find an alternative source to download these files, but I think it'd be better to attach them to this topic.

WBR,
Vitel
*


I think most people will be more interested in the ipk files rather than the source smile.gif
Vitel
QUOTE(Meanie @ Feb 13 2007, 04:13 PM)
QUOTE(Vitel @ Feb 13 2007, 08:17 AM)
Hi daniel,

zavrik.ru is temporary unavailable, sorry.
It's really nice that you've find an alternative source to download these files, but I think it'd be better to attach them to this topic.

WBR,
Vitel
*


I think most people will be more interested in the ipk files rather than the source smile.gif
*



Each one of tar.gz archives that I've attached contains the complied xfree ipk package as well as the modified .diff patches.
Meanie
QUOTE(Vitel @ Feb 14 2007, 10:32 PM)
QUOTE(Meanie @ Feb 13 2007, 04:13 PM)
QUOTE(Vitel @ Feb 13 2007, 08:17 AM)
Hi daniel,

zavrik.ru is temporary unavailable, sorry.
It's really nice that you've find an alternative source to download these files, but I think it'd be better to attach them to this topic.

WBR,
Vitel
*


I think most people will be more interested in the ipk files rather than the source smile.gif
*



Each one of tar.gz archives that I've attached contains the complied xfree ipk package as well as the modified .diff patches.
*



oh great. thanks smile.gif
i was too lazy to look inside
Meanie
QUOTE(zi99y @ Jan 5 2007, 04:18 AM)
Many thanks for updating this, I've just extracted Xfbdev as per Meanies note above and replaced the old one and so far silkscreen is working fine without the previous glitch.

Cheers!
*


does anyone have the patches listed above? the files don't exist there anymore. i want to recompile the X server with the above patches plus the caps lock patch from the BSD thread. this would give a finally perfect X server with all keys fixed, ie silkscreen
+ caps lock.
actually, if anyone else can compile it, that's probably even better since I am currently quite busy...


http://mersenne.homeunix.net/kbd.c.patch
Vitel
Hi Meanie,

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
does anyone have the patches listed above? the files don't exist there anymore.

These patches are included in the archives that are attached to my post from Feb 12 2007, 02:17 PM.

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
actually, if anyone else can compile it, that's probably even better since I am currently quite busy...

Yes, sure. I'll try to do in the near future and let you know results.

Regards,
Vitel
Meanie
QUOTE(Vitel @ Apr 2 2007, 09:51 PM)
Hi Meanie,

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
does anyone have the patches listed above? the files don't exist there anymore.

These patches are included in the archives that are attached to my post from Feb 12 2007, 02:17 PM.

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
actually, if anyone else can compile it, that's probably even better since I am currently quite busy...

Yes, sure. I'll try to do in the near future and let you know results.

Regards,
Vitel
*



thanks. i just remembered that i already downloaded those attachments and already have those patches. old age must be getting to me...

hope you will be able to compile it soon since it will take me ages otherwise...
merli
QUOTE(Meanie @ Apr 2 2007, 02:25 PM)
QUOTE(Vitel @ Apr 2 2007, 09:51 PM)
Hi Meanie,

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
does anyone have the patches listed above? the files don't exist there anymore.

These patches are included in the archives that are attached to my post from Feb 12 2007, 02:17 PM.

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
actually, if anyone else can compile it, that's probably even better since I am currently quite busy...

Yes, sure. I'll try to do in the near future and let you know results.

Regards,
Vitel
*



thanks. i just remembered that i already downloaded those attachments and already have those patches. old age must be getting to me...

hope you will be able to compile it soon since it will take me ages otherwise...
*



What about compile X with OPenGL support?
Meanie
QUOTE(merli @ Apr 2 2007, 11:40 PM)
QUOTE(Meanie @ Apr 2 2007, 02:25 PM)
QUOTE(Vitel @ Apr 2 2007, 09:51 PM)
Hi Meanie,

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
does anyone have the patches listed above? the files don't exist there anymore.

These patches are included in the archives that are attached to my post from Feb 12 2007, 02:17 PM.

QUOTE(Meanie @ Apr 1 2007, 08:41 PM)
actually, if anyone else can compile it, that's probably even better since I am currently quite busy...

Yes, sure. I'll try to do in the near future and let you know results.

Regards,
Vitel
*



thanks. i just remembered that i already downloaded those attachments and already have those patches. old age must be getting to me...

hope you will be able to compile it soon since it will take me ages otherwise...
*



What about compile X with OPenGL support?
*



no! that would be horrible. the z does not have a math co-processor nor 3D graphics accel, so opengl is best left out.
Vitel
Hi Meanie,

I've compiled XFree with all patches included, but it's not tested yet. Please verify.
psycoman
why not compile Xorg 7.2 ?
Meanie
QUOTE(psycoman @ Apr 3 2007, 11:24 AM)
why not compile Xorg 7.2 ?
*


because we are fixing the existing stuff, not building a new X server and breaking all the other working stuff...
Capn_Fish
QUOTE(Meanie @ Apr 2 2007, 09:29 PM)
QUOTE(psycoman @ Apr 3 2007, 11:24 AM)
why not compile Xorg 7.2 ?
*


because we are fixing the existing stuff, not building a new X server and breaking all the other working stuff...
*


Also, unless I'm mistaken, it is heavier than XFree.
kkazakov13
QUOTE(psycoman @ Apr 3 2007, 04:24 AM)
why not compile Xorg 7.2 ?
*


What you will benefit from it ? Except eating more memory? I'd prefer compiling kdrive.
Meanie
QUOTE(Vitel @ Apr 3 2007, 08:45 AM)
Hi Meanie,

I've compiled XFree with all patches included, but it's not tested yet. Please verify.
*



Thanks for recompilling the whole thing. However, I tried it but the patch did not have any effect. I had another look at the patch and also the entire kbd.c file and after re-evaluating what the patch does, I don't believe that it can fix the tab/caps lock issue since the lock mechanism set by xmodmap assumes that the Caps Lock and Tab keys are physically different keys, as opposed to the same physical key which represents two logical keys toggled by Fn.
At the moment, I do not have much more time to spend on this issue. I might revisit it at a later stage but not right now...
psycoman
QUOTE(kkazakov13 @ Apr 3 2007, 02:11 AM)
QUOTE(psycoman @ Apr 3 2007, 04:24 AM)
why not compile Xorg 7.2 ?
*


What you will benefit from it ? Except eating more memory? I'd prefer compiling kdrive.
*




this my question, but not have a good anwser, but fix all, to after put new thigs is a good choice, and xorg7.2 can compiled as kdrive not ?
ZDevil
I've tried the packages in Post #3 and got the screen keys working (C1000@Beta3). That's great.

But there is one (small) issue with the Calendar (XF86LaunchA) and the "Home" screen key (XF86Launch0) under Rox.

In Rox desktop, when setting keyboard shortcuts (right click desktop icon --> Edit items --> keyboard shortcut), the Calendar key is detected as "Control + XF86LaunchA) and the "Home" screen key "Control + XF86Launch0". So I cannot assign these two keys as shortcuts.T
The other keys seem to work fine.
xev also gives the correct keysym values for all keys.

What is the cause of this?
zi99y
QUOTE(ZDevil @ Apr 3 2007, 03:17 PM)
I've tried the packages in Post #3 and got the screen keys working (C1000@Beta3). That's great.

But there is one (small) issue with the Calendar (XF86LaunchA) and the "Home" screen key (XF86Launch0) under Rox.

In Rox desktop, when setting keyboard shortcuts (right click desktop icon --> Edit items --> keyboard shortcut), the Calendar key is detected as "Control + XF86LaunchA) and the "Home" screen key "Control + XF86Launch0". So I cannot assign these two keys as shortcuts.T
The other keys seem to work fine.
xev also gives the correct keysym values for all keys.

What is the cause of this?
*


Try the ipk's that from post #14 - these have been updated and work fine for me on the C3200
ZDevil
Oh, I was wrong. What I have tried are the packages in Post#14.
radiochickenwax
QUOTE(psycoman @ Apr 3 2007, 01:24 PM)
QUOTE(kkazakov13 @ Apr 3 2007, 02:11 AM)
QUOTE(psycoman @ Apr 3 2007, 04:24 AM)
why not compile Xorg 7.2 ?
*


What you will benefit from it ? Except eating more memory? I'd prefer compiling kdrive.
*




this my question, but not have a good anwser, but fix all, to after put new thigs is a good choice, and xorg7.2 can compiled as kdrive not ?
*




My impression as per this thread
http://www.oesf.org/forums/index.php?showt...hl=transparency
is that Xorg6.9 uses less memory than xfree.
I would think that since 7.2 is even more modular than 6.9, that it might take even less memory.

By the way, as to it's heaviness, xorg takes more ROM space, but less RAM space than xfree AFAIK. Sorry if this is incorrect.

I've been trying to cross-compile 6.9, from the following page:
http://www.linuxfromscratch.org/blfs/view/stable/x/xorg.html

but failing pretty consistently. (Don't currently have my output, but building up to attempting a native build from a 6000).

Another benefit of compiling xorg might be that fonts could be set up more like standard X fonts, since I haven't been able to get any new ".pfb" fonts working other than what comes with the xfree package.

It would probably be somewhat difficult to apply the pdaxrom patches to the 6.9 source. Then again, maybe not.

Last I heard, both Angstrom and OpenZaurus were using xorg7.1 with "--enable-kdrive" at compile time.
http://www.oesf.org/forums/index.php?showt...22487&hl=kdrive

http://www.oesf.org/forums/index.php?showtopic=23402&hl=#9 (post #9)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.