Re: Install latest navit on qtmoko without gpsd / GTA02
On Tuesday, January 29, 2013 08:46:13 AM robin wrote: which version of qtmoko will one be building if one clones your git tree? always the latest one (no matter if latest is stable or experimental) I try to keep master stable, but of course during releases things can break for short time. You can checkout bu tag (e.g. git checkout v50) to get what was in the release. depending on the device? I would guess eg as GTA02 and GTA04 builds are at the moment quite different that this would affect the building of the navit package as well. So if this correct will we have separate packages of navit for GTA02/GTA04? No, it's one package. The compile-time differences (#ifdef GTA04) are only in the qtmoko package. Additional apps dont have such #ifdefs. Where do you configure it that if you use dpkg-buildpackage to build navit that navit automatically gets the latest svn version to build? I used svn to git import, because i want all my apps in git on github. regarding uploding qemu buildhost, would it then be easy to keep that one in sync with your git tree? If yes, this is a good idea for entry level people like me, if not, I would rather try to build it from scratch once my wife has cleaned our harddrive to allow debian squeeze to reside in a virtual box. Yes, for releases i am just doing: git pull scripts/build-package-gta04.sh very simple and it takes a very long time ;-) Btw an old qemu buildhost is still on sf downloads [1]. But now i am using different kernel which can use 1GB of ram. Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/BuildHost/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Install latest navit on qtmoko without gpsd / GTA02
if the buildhost which can address 1gb ram builds much faster I would like to ask you to upload it so I could use that one instead. I will try to summarize what I have understood, so please correct me if I am wrong: 1.) get the buildhost to be able to compile 2.) compile qtmoko-base-system either for gta04 or gta02 with the version you want (eg v51) 3.) compile navit package, which automatically checks out the latest svn if you just want a newer version of navit, but your qtmoko-base-system version has not changed since your last build just do 3.) what would I have to do if I wanted to have one gta04 build and one gta02 build on the same machine? will they automatically have different paths? br robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and X applicatiions
Am 28.01.2013 um 02:49 schrieb Paul Wise: On Mon, Jan 28, 2013 at 7:36 AM, Neil Jerram wrote: Also, for GTA04 I think the installed xorg.conf has the wrong Why is there an installed xorg.conf at all? We are well past the days where Xorg needs a configuration file, it gained automatic configuration a long time ago. The answer is simple: there is no touchscreen calibration and debounce/dejitter method in (unconfigured) Xorg for a long time. At least I am not aware of. I.e. we have to configure Xorg to load tslib and disable autodetection of /dev/input/event*. An alternative would be to modify the touch screen kernel driver to send calibrated (and debounced, dejittered) events to the kernel. But the kernel can't read/write calibration data and adding /sys nodes to to that needs some daemon to write it. I.e. also needs some configuration. Finally, there is http://www.freedesktop.org/wiki/Software/xinput_calibrator but it is n/a in Debian so I couldn't test it quickly. BR, Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Install latest navit on qtmoko without gpsd / GTA02
On Tuesday, January 29, 2013 11:07:36 AM robin wrote: if the buildhost which can address 1gb ram builds much faster I would like to ask you to upload it so I could use that one instead. I dont know if it's much faster, but it should not be slower. And that kernel can be used also for armhf, which is nice. I will try to summarize what I have understood, so please correct me if I am wrong: 1.) get the buildhost to be able to compile Yup 2.) compile qtmoko-base-system either for gta04 or gta02 with the version you want (eg v51) Yup. 3.) compile navit package, which automatically checks out the latest svn Yes, but it does not checkout svn automatically. You have to do it manually. if you just want a newer version of navit, but your qtmoko-base-system version has not changed since your last build just do 3.) Yes. Btw the Qt/QtMoko api/abi is stable - so even builds against very old Qt will work (most of qtmoko .deb are still build against Qt 4.5 and very old QtMoko) what would I have to do if I wanted to have one gta04 build and one gta02 build on the same machine? will they automatically have different paths? Yes, the scripts/build-package-gtaXX build to different directories (build- gta02 build-gta04) so it's no problem to have them on same machine. I can try to pack the buildhost and see what will be the result size. But currently they are busy building v52 ;-) Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Upgrading QtMoko kernel
On Saturday, January 26, 2013 11:01:29 AM Radek Polak wrote: On Friday, January 25, 2013 08:32:20 PM NeilBrown wrote: On Fri, 25 Jan 2013 11:38:08 +0100 Adrien Dorsaz adr...@adorsaz.ch wrote: Hello! I've just seen this commit : https://github.com/radekp/qtmoko/commit/683ff99d7262950da179a30b59cd6b4 fa dd80454 Hmmm.. that patch is +mount -t debugfs none /sys/kernel/debug/ +echo 1 /sys/kernel/debug/pm_debug/enable_off_mode which is probably a bad idea. Most kernels will behave badly with off_mode enabled. Those for which I've fixed the various issues have Ahh oki, i have reverted it - i tought it works like that because i could see low currents even without writing 1 enable_off_mode. Btw whithout this patch the kernel twice didnt wake from suspend. Then i hacked this patch and it didnt happen again. My idea is that whithout debugfs mounted the timing during resume is different. Anyway i'll try running without the patch for a few days to check if it happens again. I did some more tests today. It happened again - but it's not that the phone didnt wake. It's more likely that only the display brightness was not restored. I plugged USB and restarted QtMoko and everything was fine. I spent rest of the day trying to reproduce it, but without success. I have also checked QtMoko resume code - it should write correct value to /sys/../backlight../brightness - maybe the call failed or write to the file failed - unfortunately i didnt have logging enabled so cant tell right now. So suspend looks fine - i tried like hundreds of times and it's stable. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and X applicatiions
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 pson...@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 n...@ossau.homelinux.net
Date: Sat, 26 Jan 2013 00:23:34 +
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 n...@ossau.homelinux.net
Date: Sat, 26 Jan 2013 01:08:55 +
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/eventN 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
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and X applicatiions
Also, for GTA04 I think the installed xorg.conf has the wrong Why is there an installed xorg.conf at all? We are well past the days where Xorg needs a configuration file, it gained automatic configuration a long time ago. not sure about X in QTMoko, but for normal X, auto conf does not work. you'll need to configure still some stuff. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and X applicatiions
An alternative would be to modify the touch screen kernel driver to send calibrated (and debounced, dejittered) events to the kernel. But the kernel can't read/write calibration data and adding /sys nodes to to that needs some daemon to write it. I.e. also needs some configuration. not quite sure, if it applies -- but there's inputattach which si supposed to act as daemon between touchscreen and X, so that X may use normal input devices/drivers. since the tslib xorg driver has a known, reported, and yet still unfixed serious bug, i'd suppose it's rather dead -- so inputattach would be the way to go anyway. i did not yet try to use it, but it's on my list for debian. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and X applicatiions
On Tuesday, January 29, 2013 05:12:45 PM Dr. H. Nikolaus Schaller wrote: 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 pson...@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 n...@ossau.homelinux.net Date: Sat, 26 Jan 2013 00:23:34 + 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; 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 General advice - try in QtMoko, if it works there search in this doc: https://github.com/radekp/qtmoko/blob/master/doc/txt/old/debian_rootfs_howto_gta04_squeeze.txt In this case you need udev running and download this rules: cd /etc/udev/rules.d wget https://raw.github.com/radekp/linux-2.6/v3.7-gta04-qtmoko-v52/GTA04/udev-rules/hso.rules wget https://raw.github.com/radekp/linux-2.6/v3.7-gta04-qtmoko-v52/GTA04/udev-rules/input.rules 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. Same general advice, just a few lines below: wget http://lindi.iki.fi/lindi/tslib/libts-0.0-0_1.0-8lindi1_armel.deb dpkg -i libts-0.0-0_1.0-8lindi1_armel.deb Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and X applicatiions
Am 30.01.2013 um 07:39 schrieb Radek Polak: On Tuesday, January 29, 2013 05:12:45 PM Dr. H. Nikolaus Schaller wrote: 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 pson...@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 n...@ossau.homelinux.net Date: Sat, 26 Jan 2013 00:23:34 + 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; 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 General advice - try in QtMoko, if it works there search in this doc: https://github.com/radekp/qtmoko/blob/master/doc/txt/old/debian_rootfs_howto_gta04_squeeze.txt In this case you need udev running and download this rules: cd /etc/udev/rules.d wget https://raw.github.com/radekp/linux-2.6/v3.7-gta04-qtmoko-v52/GTA04/udev-rules/hso.rules wget https://raw.github.com/radekp/linux-2.6/v3.7-gta04-qtmoko-v52/GTA04/udev-rules/input.rules Ok, the second rule was missing. 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. Same general advice, just a few lines below: wget http://lindi.iki.fi/lindi/tslib/libts-0.0-0_1.0-8lindi1_armel.deb dpkg -i libts-0.0-0_1.0-8lindi1_armel.deb This also works: apt-get source libts-0.0-0 sed -i s/0x01/0x010001/g /usr/include/linux/input.h ( cd tslib-1.0 dpkg-buildpackage -uc -b ) sed -i s/0x010001/0x01/g /usr/include/linux/input.h dpkg -i libts-0.0-0_1.0-7_armel.deb but certainly needs more time than wget :) Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
