QtMoko and X applicatiions

Dr. H. Nikolaus Schaller hns at goldelico.com
Tue Jan 29 17:12:45 CET 2013


Hi,
using the new 3.7 kernel with debian squeeze Xorg also makes troubles...

Am 28.01.2013 um 00:36 schrieb Neil Jerram:

> Radek Polak <psonek2 at seznam.cz> writes:
> 
>> On Friday, January 25, 2013 04:37:05 PM Iain B. Findleton wrote:
>> 
>>> Thanks for the hint.
>>> 
>>> When I start QM from the qtmoko menu, I get nothing but a blank screen
>>> and an input for an application. I have updated the files in
>>> /opt/qtmoko/etc/qm as described in the Openmoko wiki, but the menu items
>>> for favourites shows nothing. Is there any other updated documentation?
>>> Need I install something?
>> 
>> Install your favourite X application - e.g. foxtrotgps and then select 
>> "Favourites" from context menu. The application should appear there (if it has 
>> .desktop file in /usr/share/applications). Then you can also configure it some 
>> more - like fullscreen, virtiual keyboard...
> 
> It seems to me that there are a couple of problems here; please see the
> attached patches.
> 
> From 2764304b0a4ad50e608f57bb00ecc1388217b9fc Mon Sep 17 00:00:00 2001
> From: Neil Jerram <neil at ossau.homelinux.net>
> Date: Sat, 26 Jan 2013 00:23:34 +0000
> Subject: [PATCH 1/3] qx - fix setting of DISPLAY variable
> 
> ---
> src/3rdparty/applications/qx/qx.cpp |    2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/3rdparty/applications/qx/qx.cpp b/src/3rdparty/applications/qx/qx.cpp
> index 6c22ba1..65a651e 100644
> --- a/src/3rdparty/applications/qx/qx.cpp
> +++ b/src/3rdparty/applications/qx/qx.cpp
> @@ -172,7 +172,7 @@ QX::QX(QWidget *parent, Qt::WFlags f)
>     screen = QX::ScreenMain;
> 
>     if(getenv("DISPLAY") == NULL)
> -        setenv("DISPLAY", "0:0", true);
> +        setenv("DISPLAY", ":0.0", true);
> 
> #if QTOPIA
>     powerConstraint = QtopiaApplication::Disable;
> -- 
> 1.7.10.4
> 
> From f2b60da8feb85ff28b1653a7e2c626fcee332db2 Mon Sep 17 00:00:00 2001
> From: Neil Jerram <neil at ossau.homelinux.net>
> Date: Sat, 26 Jan 2013 01:08:55 +0000
> Subject: [PATCH 3/3] qx - fix Xfbdev invocation
> 
> It wants "-nocursor", not "-hide-cursor".
> ---
> src/3rdparty/applications/qx/qx.cpp |    5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/src/3rdparty/applications/qx/qx.cpp b/src/3rdparty/applications/qx/qx.cpp
> index 65a651e..bdc01c0 100644
> --- a/src/3rdparty/applications/qx/qx.cpp
> +++ b/src/3rdparty/applications/qx/qx.cpp
> @@ -438,12 +438,15 @@ void QX::runApp(QString filename, QString applabel, bool rotate)
>         }
>         else
>         {
> +#ifdef QT_QWS_NEO
>             args.append("-hide-cursor");
>             args.append("-dpi");
>             args.append("128");
> -#ifdef QT_QWS_NEO
>             xprocess->start("/usr/bin/Xglamo", args);
> #else
> +            args.append("-nocursor");
> +            args.append("-dpi");
> +            args.append("128");
>             xprocess->start("/usr/bin/Xfbdev", args);
> #endif
>         }
> -- 
> 1.7.10.4
> 
> 
> Possibly these affect GTA04 only though; I'm not sure.
> 
> Also, for GTA04 I think the installed xorg.conf has the wrong
> /dev/input/event<N> numbers.  For GTA04 I believe it should be

the event-numbers have changed between 2.6.32 and 3.7 kernels.

>  touchscreen = 0
>  Power = 2
>  AUX = 5
> although I suppose even better would be to use the symlinks
>  /dev/input/touchscreen
>  /dev/input/power
>  /dev/input/aux

Yes, definitively. The event numbers aren't guaranteed.

> Are those symlinks created on Freerunner too?  If so, that's the best
> overall solution.

Hm. How do you get these symlinks? On my 3.7 system they are not
created automatically at all. And the touch is even missing in

/dev/input/by-name

> 
> Also what's the latest thinking on which is best for GTA04, out of Xorg
> and Xfbdev?  I currently have Xfbdev installed, but I don't remember why
> I made that choice.
> 
> Regards,
>        Neil

Another issue is that evtouch (from debian squeeze) is segfaulting.
And tslib (also from squeeze) is no longer recognizing any events
since the kernel presents a different EV_VERSION.

Nikolaus




More information about the community mailing list