Re: [QtMoko] Error compiling on wheezy
Radek Polak pson...@seznam.cz writes: i have now updated the build instructions. After many problems with wheezy as host i have decided that the recommended way to install qtmoko is now chroot. It should avoid the problem with different packages/versions on the hosts - and also the build HOWTO is a lot easier: https://github.com/radekp/qtmoko/blob/master/README I can now build the image in the chroot, but still there are some problems when i run it on GTA04. I'll investigate what is wrong. You can try yourself and report if it worked. Starting from efdad160239fca2e192553ee85b2da47851d3a90, I needed the attached patch to get a successful build (exactly following the README instructions). From 70619ca91f15f2dabfaaeaa9d941ee71674e5518 Mon Sep 17 00:00:00 2001 From: Neil Jerram n...@ossau.homelinux.net Date: Sun, 4 Nov 2012 12:03:07 + Subject: [PATCH 1/9] Successful chroot building --- scripts/qtmoko-chroot.sh |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/scripts/qtmoko-chroot.sh b/scripts/qtmoko-chroot.sh index f4b812d..62d9c8f 100755 --- a/scripts/qtmoko-chroot.sh +++ b/scripts/qtmoko-chroot.sh @@ -34,7 +34,9 @@ then fi echo Installing chroot packages -cdebootstrap --flavour=minimal --include=build-essential,git,openssh-client,ccache,locales,procps,psmisc,libxext-dev,libasound2-dev,libdbus-1-dev,libssl-dev,libts-dev,libbluetooth-dev,libxtst-dev,libpng12-dev,libjpeg8-dev,libv4l-dev,libspeexdsp-dev,libglib2.0-dev,libsqlite3-dev,quilt squeeze ../qtmoko-chroot http://cdn.debian.net/debian/ +until cdebootstrap --flavour=minimal --include=build-essential,git,openssh-client,ccache,locales,procps,psmisc,libxext-dev,libasound2-dev,libdbus-1-dev,libssl-dev,libts-dev,libbluetooth-dev,libxtst-dev,libpng12-dev,libjpeg8-dev,libv4l-dev,libspeexdsp-dev,libglib2.0-dev,libsqlite3-dev,quilt,libgstreamer0.10-dev,libgstreamer-plugins-base0.10-dev squeeze ../qtmoko-chroot http://cdn.debian.net/debian/; do + : +done fi if [ ! -d ../qtmoko-chroot/proc/bus ] -- 1.7.10.4 After that I found that qpe.sh didn't start up at all on the phone, with messages indicating not being able to find libgstapp-0.10.so.0. Doing 'apt-get install gstreamer0.10-plugins-base' appears to have fixed that. Next, I found that the theme had reverted to Finxi, but for some reason even Finxi isn't fully installed: if I click the icon for the main menu, only the Games, Apps and Docs icons are there; the other grid positions are either empty or generic grey file icons with a ?. Then I did s/finxi/mokofaen/g in /opt/qtmoko/etc/default/Trolltech/qpe.conf, and restarted the phone. This successfully switched the theme to Mokofaen, but I still have missing icons as described above. Also I don't think it's just an icon problem, because if I click on the place where the Message icon normally is, I get an error popup saying No application is defined for this document. Any thoughts/ideas? Thanks, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: openphoenux review on mobilejournal.net
right On Thu, 01 Nov 2012 13:25:00 +0100, Christoph Pulster openm...@pulster.de wrote: They are right that the price is high. There is no price tag too high for FREEDOM. May Apple/Androids fuck their fanboys with any backdoor implemented. Christoph -- 不要催我!你曾經問過梵谷畫很快嗎? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
On Sunday, November 04, 2012 02:00:32 PM Neil Jerram wrote: Starting from efdad160239fca2e192553ee85b2da47851d3a90, I needed the attached patch to get a successful build (exactly following the README instructions). Hi Neil, it's applied now [1], thanks! Radek [1] https://github.com/radekp/qtmoko/commit/cbb787a61c74332e9676a0b3dc1c069d70971137 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
WikiReader Arduino shield (or generic serial touchscreen)
I've gotten rather excited recently about the wikireader since they
can be had for under $15, and this looks like an ideal platform to
make a nice touchscreen interface for home automation and other things
you might want to do with other open hardware like the Arduino.
I started by hooking up the serial port to a board with a PIC
microcontroller with Ethernet, and thanks to the recent updates
of the schematics, it appears I can power the PIC board I have
just fine (but it will probably eat batteries quickly).
What I'm trying to figure out now is how to get some reasonable UI
abstraction layer that functions over serial. There are things like
https://www.sparkfun.com/products/10089 , which is a lot like what
I'd like, but I want to have a fully open protocol that the
Wikireader hardware runs, draws buttons graphs, and then responds
over serial when someone presses one of the buttons on the screen.
I started hacking up the wikireader/samo-lib/grifo/examples/lcd code
(diff attached later), and I can (using an ftdi serial), get stuff
to show up on the screen.
What I'd really like to be able to do though, is fix the simulator
code so I can try out UI protocol development without having to load
new code on an SDcard all the time. What I'm stuck with right now
is if I include console.h, and the console library, things work on
the real hardware, but the lcd/simulate version doesn't build, so I
need to figure out how to add that to both.
Has anyone else tried this out recently, and what would be a good
mailing list to get some technical discussions started again?
I've also wondered if I can do some hackery to have a PIC or arduino
'pretend' to be an SDcard, and then I could imagine a board that
would just plug right into a stock Wikireader SD card slot with
an adapter cable, and require no soldering or even opening of the
case.
Thoughs anyway, or better ideas ?
Thanks
-- Troy
diff -r 8baa4bcce346 samo-lib/grifo/examples/lcd/lcd.c
--- a/samo-lib/grifo/examples/lcd/lcd.c Tue Oct 30 10:02:23 2012 +0800
+++ b/samo-lib/grifo/examples/lcd/lcd.c Sun Nov 04 23:20:17 2012 -0600
@@ -20,6 +20,7 @@
*/
#include grifo.h
+#include console.h
int grifo_main(int argc, char *argv[])
{
@@ -28,55 +29,13 @@
int x;
int y;
+ int x1;
+ int y1;
+ int x2;
+ int y2;
debug_printf(lcd start\n);
- debug_printf(black screen\n);
- lcd_clear(LCD_BLACK);
- delay_us(100);
-
- debug_printf(plot white pixels\n);
- for (x = 10, y = 10; x 100; x += 5, y += 10) {
- lcd_point(x, y);
- }
- delay_us(100);
-
- debug_printf(draw white lines\n);
- lcd_move_to( 10, 10);
- lcd_line_to(120, 10);
- lcd_line_to(120, 100);
- lcd_line_to( 10, 100);
- lcd_line_to( 10, 10);
-
- lcd_move_to( 10, 10);
- lcd_line_to(120, 100);
- lcd_move_to(120, 10);
- lcd_line_to( 10, 100);
- delay_us(100);
-
- debug_printf(white screen\n);
- lcd_clear(LCD_WHITE);
- delay_us(100);
-
- debug_printf(plot black pixels\n);
- for (x = 150, y = 140; x 200; x += 10, y += 5) {
- lcd_point(x, y);
- }
- delay_us(100);
-
- debug_printf(draw black lines\n);
- lcd_move_to( 10, 10);
- lcd_line_to(120, 10);
- lcd_line_to(120, 100);
- lcd_line_to( 10, 100);
- lcd_line_to( 10, 10);
-
- lcd_move_to( 10, 10);
- lcd_line_to(120, 100);
- lcd_move_to(120, 10);
- lcd_line_to( 10, 100);
- delay_us(100);
-
debug_printf(eye pattern\n);
lcd_clear(LCD_WHITE);
@@ -94,90 +53,21 @@
debug_printf(text rows %d\n, lcd_max_rows());
debug_printf(text columns %d\n, lcd_max_columns());
- debug_printf(positioned text\n);
- lcd_clear(LCD_WHITE);
- lcd_at_xy(20, 8);
- lcd_print(one);
- delay_us(50);
-
- lcd_at_xy(3, 1);
- lcd_print(two);
- delay_us(50);
-
- lcd_at_xy(0, 0);
- lcd_print(A);
- delay_us(50);
-
- lcd_at_xy(lcd_max_columns() - 1, lcd_max_rows() - 1);
- lcd_print(Z);
- delay_us(200);
-
- debug_printf(black text\n);
- lcd_clear(LCD_WHITE);
- lcd_print(This the first is a line of text\n);
- lcd_print(This the second is a line of text\n);
- lcd_print(This the third is a line of text\n);
- lcd_print(This the fourth is a line of text\n);
- lcd_print(This the fifth is a line of text\n);
- lcd_printf(some numbers: %d 0x%08x\n, 12345, 349599327);
- delay_us(200);
-
- debug_printf(white text\n);
- lcd_clear(LCD_BLACK);
- lcd_print(This the first is a line of text\n);
- lcd_print(This the second is a line of text\n);
- lcd_print(This the third is a line of text\n);
- lcd_print(This the fourth is a line of text\n);
- lcd_print(This the fifth is a line of text\n);
- lcd_printf(some numbers: %d 0x%08x\n, 12345, 349599327);
- delay_us(200);
-
- debug_printf(mixed text\n);
- lcd_clear(LCD_WHITE);
- lcd_print(This the first is a line of text\n);
- (void)lcd_set_colour(LCD_WHITE);
- lcd_print(This the second is a line of text\n);
- (void)lcd_set_colour(LCD_BLACK);
- lcd_print(This the third is a line of text\n);
- (void)lcd_set_colour(LCD_WHITE);
- lcd_print(This the fourth is a line of text\n);
-
Re: WikiReader Arduino shield (or generic serial touchscreen)
Hello Troy, On Mon, Nov 5, 2012 at 6:54 AM, Troy Benjegerdes ho...@hozed.org wrote: What I'd really like to be able to do though, is fix the simulator code so I can try out UI protocol development without having to load new code on an SDcard all the time. What I'm stuck with right now is if I include console.h, and the console library, things work on the real hardware, but the lcd/simulate version doesn't build, so I need to figure out how to add that to both. I have a virtual machine laying around at home that builds and runs the WikiReader simulator. Perhaps I can try to integrate your diffs and see what goes wrong. Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
