**** BEGIN LOGGING AT Wed Oct 05 02:59:58 2011 Oct 05 03:17:38 does anyone know if the phone/data connection features of SHR work on female phones...I know the wiki says yes to the palm pre but I wanted to be sure before I started playing around Oct 05 03:18:49 gah I meant CDMA stupid auto text Oct 05 05:13:29 seems they use a similar protocol Oct 05 05:13:41 could try #webos-internals if mickeyl is not around Oct 05 05:25:07 Slyon: I think so, yeah Oct 05 06:43:06 DocScrutinizer: the sysfs path is still wrong Oct 05 06:43:22 gathered as much Oct 05 06:43:43 [2011-10-04 14:45:46] lindi-: also what's the correct path for new kernel? Oct 05 06:44:07 whoa! xpra org.freedesktop.Notification forwarding that was added to svn almost works Oct 05 06:44:25 (got an empty notification popup on my remote machine when you highlighted me) Oct 05 06:45:29 got busy with claiming another free Nokia device :-D Oct 05 06:46:00 DocScrutinizer: /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/hdq/hdq/dump Oct 05 06:46:07 DocScrutinizer: but I'm not sure if you should use some symlink Oct 05 06:46:56 DocScrutinizer: could you also add some some "For more information see the datasheet XYZ.pdf"? Oct 05 06:47:27 this is now the second time that my battery refuses to fully charge :) Oct 05 06:47:39 I do have spare batteries but still interesting Oct 05 06:49:43 symlink?? Oct 05 06:50:03 DocScrutinizer: /sys has a lot of symlinks Oct 05 06:50:12 nah, I'll not require a symlink, I'll check what's available Oct 05 06:50:18 aaah Oct 05 06:50:32 DocScrutinizer: so it is not entirely clear which path is going to survive best Oct 05 06:51:24 /sys/bus/platform/devices/hdq ../../../devices/platform/s3c2440-i2c/i2c-0/0-0073/hdq Oct 05 06:51:38 /sys/class/power_supply/battery ../../devices/platform/s3c2440-i2c/i2c-0/0-0073/hdq/bq27000-battery.0/power_supply/battery Oct 05 06:52:07 I'll probably find the /sys/ * *hdq* /dump pathname Oct 05 06:52:41 omhacks started when I had accumulated enough such things that my bootup was very slow :) Oct 05 06:53:03 good point Oct 05 06:54:51 you noticed you can pass the pathname as $1? Oct 05 06:55:24 yep Oct 05 06:55:39 maybe /sys/bus/platform/drivers/hdq/hdq/hdq/dump is more sane default? Oct 05 06:56:00 noticed Oct 05 06:56:43 might even work with 2.6.29-rc2 too Oct 05 09:13:16 freesmartphone.org: 03morphis 07cornucopia * r2725c6c18cac 10/libfsotransport/fsotransport/crespo.vala: libfsotransport: be more verbose in crespo modem transport Oct 05 09:13:56 heyho Oct 05 09:37:19 mickey|office: good morning! Oct 05 09:50:32 good morning all Oct 05 14:43:19 GNUtoo|laptop: heyho Oct 05 14:43:38 GNUtoo|laptop: I had the modem up with a fso image Oct 05 14:43:48 GNUtoo|laptop: on nexus s Oct 05 14:43:56 and I've xorg Oct 05 14:44:04 but pointer doesn't click yet Oct 05 14:44:13 maybe that's because of xf86-input-mtev Oct 05 14:44:30 I ported it forward to API xorg > 12 Oct 05 14:44:35 or ABI Oct 05 14:44:38 I don't remember Oct 05 14:47:52 SHR: 03morphis 07meta-smartphone * re5a99b737dc6 10/meta-fso/recipes-freesmartphone/serial-utils/ (pty-forward-native.bb serial-forward_git.bb): meta-fso: serial-utils: bump SRCREV Oct 05 14:47:53 SHR: 03morphis 07meta-smartphone * r85b72717ed4e 10/meta-samsung/recipes-kernel/linux/linux-samsung-crespo_git.bb: meta-samsung: linux-samsung-crespo: we want zImage as kernel image type not uImage Oct 05 14:47:53 SHR: 03morphis 07meta-smartphone * rafc8f19915fb 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: remove unneeded qt4 tslib input driver Oct 05 14:47:57 SHR: 03morphis 07meta-smartphone * re8cba73b8ebe 10/meta-palm/recipes-core/initscripts/initscripts_1.0.bbappend: meta-palm: initscripts: add documenation about additional initscript Oct 05 14:47:57 SHR: 03morphis 07meta-smartphone * r5fc68c90d5cf 10/meta-samsung/conf/machine/crespo.conf: meta-samsung: crespo machine: prefer xserver-xorg as xserver Oct 05 14:47:59 SHR: 03morphis 07meta-smartphone * r5be5d71c52c2 10/meta-samsung/recipes-core/initscripts/initscripts_1.0.bbappend: meta-samsung: initscripts: add documentation about additional initscripts Oct 05 14:47:59 SHR: 03GNUtoo 07meta-smartphone * ra9da197ce81c 10/meta-aurora/recipes-aurora/images/aurora-image.bb: meta-aurora: aurora-image: remove non-existing qt4-embedded-plugin-sqldriver-sqlite2 dependency Oct 05 14:48:13 GNUtoo|laptop: mtev? Oct 05 14:48:58 multi touch event Oct 05 14:49:02 ah ok Oct 05 14:49:10 I think it register one click down Oct 05 14:49:17 but then doesn't register any click up Oct 05 14:49:17 but I can use the touchscreen input node with std. input drivers? Oct 05 14:49:25 maybe Oct 05 14:49:26 how? Oct 05 14:49:30 ah you didn't try Oct 05 14:49:33 no Oct 05 14:49:37 well It doesn't register the clicks Oct 05 14:49:41 I just compiled an aurora-image Oct 05 14:49:44 for the nexus s Oct 05 14:49:46 ok Oct 05 14:50:03 I tried to modify kernel driver => failure Oct 05 14:50:35 basically renaming something like MT_TOUCH (don't remember the exact name) make it disapear Oct 05 14:52:43 so aurora is up Oct 05 14:53:43 ok Oct 05 14:53:47 touchscreen works in aurora? Oct 05 14:54:07 btw I also succedded at booting my own kernels Oct 05 14:54:08 the cursor moved from the middle of the screen to the top left corner Oct 05 14:54:11 but nothing more Oct 05 14:54:13 yeah Oct 05 14:54:16 ok Oct 05 14:54:17 it was the hex thing? Oct 05 14:54:20 yes Oct 05 14:54:21 with mkbootimg? Oct 05 14:54:23 yes Oct 05 14:54:24 :) Oct 05 14:54:33 you didn't used the mkbootimg from fso? Oct 05 14:54:42 it's too old Oct 05 14:54:49 ok Oct 05 14:54:50 no --page size in fso Oct 05 14:55:00 I used the one from replicant Oct 05 14:55:03 I added it Oct 05 14:55:07 ok nice Oct 05 14:55:23 thanks to unbootimg btw Oct 05 14:55:30 but didn't pushed .. Oct 05 14:55:33 no problem Oct 05 14:55:45 ok Oct 05 14:56:04 unbootimg is not from you but from another porter if I remember well Oct 05 14:56:09 so thanks to him Oct 05 14:56:58 freesmartphone.org: 03morphis 07utilities * rb4da9e72d550 10/android/image-utils/mkbootimg/mkbootimg.c: android: mkbootimg: add --pagesize command line argument Oct 05 14:58:07 yes Oct 05 14:58:12 but I pushed it Oct 05 15:00:03 freesmartphone.org: 03morphis 07aurora * r005b06e1b67f 10/aurora-daemon/src/rootwindow.cpp: aurora-daemon: fix path to /dev/fb0 Oct 05 15:00:10 ok so thanks too Oct 05 15:21:26 GNUtoo|laptop: do you know the name of the kernel driver responsible for the touchscreen? Oct 05 15:21:37 yes Oct 05 15:22:04 drivers/input/touchscreen/mxt224.c Oct 05 15:23:54 thanks Oct 05 15:35:05 GNUtoo|laptop: ok, it should be possible to use the touchscreen with qt4 as it provides std. linux input events Oct 05 15:35:16 just with the additional information about the finger used Oct 05 15:35:50 ah? Oct 05 15:36:09 do you have more details? Oct 05 15:36:13 GNUtoo|laptop: the drivers just reports a sync event Oct 05 15:36:18 no up or down event Oct 05 15:36:32 ah? Oct 05 15:37:04 it uses ABS_MT_POSITION_X, ABS_MT_POSITION_Y, ABS_MT_TOUCH_MAJOR, ABS_MT_WIDTH_MAJOR Oct 05 15:37:15 and ABS_MT_TRACKING_ID Oct 05 15:37:19 Event: time 2962.179338, type 3 (Absolute), code 48 (Touch Major), value 83 Oct 05 15:37:25 Event: time 2962.247822, type 3 (Absolute), code 48 (Touch Major), value 0 Oct 05 15:37:28 what's that then? Oct 05 15:37:43 that's like a BTN_TOUCH Oct 05 15:38:33 seems so Oct 05 15:39:13 isn't there a userspace implementation in android for this? Oct 05 15:39:23 xf86-input-mtev Oct 05 15:39:41 in the worse case scenario you use X Oct 05 15:39:57 it's a 1GHz CPU, with not-openmoko like graphics.... Oct 05 15:40:08 so it should handle QT, right? Oct 05 15:40:26 yes Oct 05 15:40:43 but X is somewhat oversized for aurora Oct 05 15:40:52 we just need it to display one window Oct 05 15:40:59 so I didn't thought until about using it Oct 05 15:44:18 GNUtoo|laptop: interesting: http://developer.qt.nokia.com/forums/viewthread/5052 Oct 05 15:44:37 GNUtoo|laptop: and https://www.kernel.org/doc/Documentation/input/multi-touch-protocol.txt Oct 05 15:46:00 kernel seem fine Oct 05 15:46:13 it's that xf86-input-mtev that is not fine Oct 05 16:17:46 hm Oct 05 16:30:20 Good afternoon Oct 05 16:43:32 angelox|laptop: heyho Oct 05 16:43:55 GNUtoo|laptop: I can work around mtev for the first with creating a simple tslib driver which ignores all events with tracking_id != 0 Oct 05 16:44:35 ok Oct 05 16:44:45 if you can do that.... Oct 05 16:44:55 why not fix xf86-input-mtdev? Oct 05 16:45:05 it's straingtforward if you know xorg Oct 05 16:45:39 yes Oct 05 16:45:56 hm Oct 05 16:46:44 here's my diff: Oct 05 16:46:45 http://www.pastie.org/private/9w7ivn2tjkibr1l1fjnwvw Oct 05 16:46:54 it's for compiling with recent xorg Oct 05 16:47:05 then let's talk about the problematic part Oct 05 16:47:09 it works now? Oct 05 16:47:10 when I touch the screen Oct 05 16:47:26 it compiles, run but fails to click normally, let me explain Oct 05 16:47:40 when pressing a button Oct 05 16:47:46 it register a button click Oct 05 16:47:51 but then nothing Oct 05 16:48:15 it doesn't release it Oct 05 16:48:20 so that blocks the whole thing Oct 05 16:48:40 https://gitorious.org/xf86-input-mtev Oct 05 16:48:44 that's the one I used Oct 05 16:49:16 here: https://gitorious.org/xf86-input-mtev/xf86-input-mtev/blobs/master/src/multitouch.c Oct 05 16:49:34 near line 326 there are some stuff Oct 05 16:49:40 I guess it's for handing the button down Oct 05 16:49:56 but I've no idea why my button up code doesn't work Oct 05 16:50:00 I tried inserting that: Oct 05 16:50:14 xf86PostButtonEvent(local->dev, TRUE, 1, 0, 0, 0); Oct 05 16:50:20 with a 0 right after the 1 Oct 05 16:50:35 and change down to 0 in other stuff near it Oct 05 16:50:39 like for instance: Oct 05 16:50:43 xf86PostButtonEvent(local->dev, TRUE, 1, 1, 0, 0); Oct 05 16:50:44 xf86PostButtonEvent(local->dev, TRUE, 1, 0, 0, 0); Oct 05 16:51:31 morphis, ^^^ Oct 05 16:52:11 same for other lines under if(down && pdown == 0) and else if (down == 0 && pdown) Oct 05 17:10:46 morphis, ping? Oct 05 17:10:54 should I continue to work on it? Oct 05 17:11:00 do you want my recipe? Oct 05 17:14:17 I wish I could help with this… is it something I can easily cross-compile without all the SHR build environment but only the cross-compilers, and test on the top of an image someone else built? Oct 05 17:26:40 I've a recipe Oct 05 17:26:46 and you need to know xorg a bit Oct 05 17:38:57 ok Oct 05 17:41:04 morphis, ping? Oct 05 17:41:19 GNUtoo|laptop: sorry, was out for launch Oct 05 17:41:22 ok Oct 05 17:41:24 np Oct 05 17:41:27 s/launch/lunch/ Oct 05 17:41:27 morphis meant: GNUtoo|laptop: sorry, was out for lunch Oct 05 17:41:51 I'll pastebin the recipe Oct 05 17:42:16 ok Oct 05 17:42:27 we should push it to meta-oe later Oct 05 17:43:37 in general it should be no problem to run aurora with x11 Oct 05 17:44:00 I just need to make it the fullscreen window Oct 05 17:44:08 http://www.pastie.org/private/ws5tu2uzaf3cdb07j3gmw Oct 05 17:44:20 GNUtoo|laptop: btw do we have any chance to get the pvr running with X11 with the binaries from android? Oct 05 17:44:51 GNUtoo|laptop: we should append your patch in meta-shr Oct 05 17:45:09 morphis, not with the android drivers Oct 05 17:45:28 you mean the gles libraries? Oct 05 17:45:31 android drivers are proprietary and depends on bionic(the android libc) Oct 05 17:45:36 yes Oct 05 17:45:40 ah damn it Oct 05 17:45:48 with palms libraries I got it Oct 05 17:45:55 but bionic is bad Oct 05 17:45:55 let's see that later Oct 05 17:46:16 if you do it please don't infect the standard fso/shr etc... Oct 05 17:46:33 I will not Oct 05 17:46:36 ok Oct 05 17:46:40 but thats something I will try very late Oct 05 17:46:43 ok Oct 05 17:46:47 we have now other problems Oct 05 17:46:51 angelox|laptop: ping Oct 05 17:46:51 let's first concentrate on getting touch Oct 05 17:47:02 morphis, so will you look at that touch driver? Oct 05 17:47:08 yes Oct 05 17:47:09 xf86-input-mtdev? Oct 05 17:47:11 ok Oct 05 17:47:12 nice Oct 05 17:47:21 just need to get aurora ported to x11 Oct 05 17:47:26 but that should be done very fast Oct 05 17:47:42 just the build will need some time Oct 05 17:47:53 cause of qt4 recompilation Oct 05 17:48:02 ok Oct 05 17:48:12 I just need touchscreen for now Oct 05 17:48:18 to progress in my port Oct 05 17:48:31 should I push updated defconfig? Oct 05 17:48:37 with x11 support Oct 05 17:52:15 yes please Oct 05 17:52:35 and can you take a look at suspend? Oct 05 17:53:01 as you have more experience with suspend on android devices Oct 05 17:57:49 angelox|laptop: ping Oct 05 18:00:28 yes Oct 05 18:00:30 I'll do Oct 05 18:00:38 morphis: pong Oct 05 18:00:39 I need to look at wifi too Oct 05 18:01:04 it's a bcm4329 and I was told by alex[sp3dev] to import a mainline or staging driver Oct 05 18:01:11 rather than try to fix it Oct 05 18:01:58 btw I need X for suspend Oct 05 18:02:04 I must be sure suspend works with X Oct 05 18:03:00 bbl Oct 05 18:03:16 seem to work fine Oct 05 18:03:23 echo mem > /sys/power/state Oct 05 18:03:28 echo on > /sys/power/state Oct 05 18:03:33 resumes the pannel Oct 05 18:06:16 morphis: sorry,i was out buying stuff in market and forgot put away here :) Oct 05 18:07:23 GNUtoo|laptop: ok, but we should put the driver in our kernel tree Oct 05 18:07:46 GNUtoo|laptop: which is based on cyanogenmods kernel and already has the kernel driver for the bcm4329 Oct 05 18:07:50 angelox|laptop: no problem Oct 05 18:07:58 angelox|laptop: I saw your work about the keyboard Oct 05 18:08:04 morphis, we should do things in order, suspend later(since it depends on telephony, xorg etc...) Oct 05 18:08:20 morphis, it's in the tree Oct 05 18:08:29 GNUtoo|laptop: ok Oct 05 18:08:43 angelox|laptop: one thing: please follow general qt code style Oct 05 18:08:54 angelox|laptop: so a keyBoard instead of key_board Oct 05 18:09:22 GNUtoo|laptop: ok, so what are the things we're doing now Oct 05 18:09:29 me: telephony + touchscreen Oct 05 18:09:41 what do you want me to do? Oct 05 18:10:02 what do you think is most important? Oct 05 18:10:03 audio? Oct 05 18:10:07 wifi? Oct 05 18:10:11 wifi Oct 05 18:10:20 a boot image? Oct 05 18:10:24 yes boot image Oct 05 18:10:40 audio is just a mather of compiling gstreamer and testing it Oct 05 18:10:42 so for you: boot image, wifi, audio ? Oct 05 18:10:48 there are state files to do too Oct 05 18:10:52 yes Oct 05 18:10:55 ok Oct 05 18:11:13 I will put my notes into the fso wiki Oct 05 18:11:16 I'll push my defconfig soon Oct 05 18:11:17 ok Oct 05 18:12:45 morphis: ok,but where did i use that? Oct 05 18:12:51 * angelox|laptop doesn't remember... Oct 05 18:13:27 angelox|laptop: in your keyboard c++ code and in qml Oct 05 18:13:44 GNUtoo|laptop: ok Oct 05 18:15:03 morphis: hmm ok..like using kbdView instead kbd_view... Oct 05 18:15:12 yes Oct 05 18:15:20 just to have a common code style Oct 05 18:15:30 GNUtoo|laptop: aurora-image with x11 is building now Oct 05 18:15:54 morphis: ok,please excuse me Oct 05 18:23:02 morphis: do i use curly braces with if-else statements with just one line? Oct 05 18:37:46 morphis: may i use http://developer.qt.nokia.com/wiki/Qt_Coding_Style ? Oct 05 18:38:42 angelox|laptop: { in their own line please :) Oct 05 18:39:38 angelox|laptop: and no if-else in _one_ line Oct 05 18:48:53 hmm Oct 05 18:49:04 then: Oct 05 18:49:08 if(reason) Oct 05 18:49:09 { Oct 05 18:49:13 do stuff; Oct 05 18:49:13 } Oct 05 18:49:15 else Oct 05 18:49:16 { Oct 05 18:49:19 do another stuff; Oct 05 18:49:20 } Oct 05 18:49:26 is inacceptable? Oct 05 18:49:44 ? Oct 05 18:49:51 that is almost perfect :-) Oct 05 18:49:59 perfect would be: if ( reason ) Oct 05 18:50:41 then that way i can use one line in each statement? Oct 05 18:50:42 and of course content between braces needs indentation of 4 *spaces* Oct 05 18:51:37 - no if (foo) do bar; (in one line) Oct 05 18:51:45 - braces on a line of their own Oct 05 18:51:53 is what fso uses Oct 05 18:52:06 hmm Oct 05 18:52:09 with the exception of _very_ simple if's don't need braces Oct 05 18:52:16 like: Oct 05 18:52:20 if ( err ) Oct 05 18:52:22 return; Oct 05 18:52:33 but that is upon your taste Oct 05 18:52:39 you can put braces there as well Oct 05 18:52:41 if ( err ) Oct 05 18:52:42 { Oct 05 18:52:44 return; Oct 05 18:52:44 } Oct 05 18:52:59 * angelox|laptop apologizes for his bad understanding Oct 05 18:53:04 np Oct 05 18:53:13 ok..now i understand... thanks Oct 05 18:53:15 angelox|laptop: what editor do you use? Oct 05 18:53:33 i do use Qt IDE Oct 05 18:53:40 ahh, ok Oct 05 18:53:57 important thing is to be consistent with indentation Oct 05 18:54:01 4 spaces Oct 05 18:54:04 no tabs Oct 05 18:54:13 I couldn't switch fully to command line because i don't trust myself in that task :) Oct 05 18:54:14 is what fso uses Oct 05 18:54:20 :) Oct 05 18:54:32 it does replace tab to 4 spaces,then it's ok i guess :) Oct 05 18:55:34 yup Oct 05 18:57:11 if i have another question,i'll check fso codes :) Oct 05 18:57:54 angelox|laptop: that is a good place to check, yeah :-) Oct 05 19:22:22 Hello i need help with the shr n900 is there anybody who could help me? Oct 05 19:29:22 heh, that was a tad to short of waiting ;) Oct 05 19:59:27 freesmartphone.org: 03angelo 07aurora * r181cfa494d48 10/aurora-daemon/src/ (application.cpp virtualkeyboard.cpp virtualkeyboard.h): aurora-daemon: add error handling into daemon Oct 05 19:59:28 freesmartphone.org: 03angelo 07aurora * r4f3cbda7d3f2 10/aurora-daemon/src/rootwindow.cpp: Merge branch 'master' of git.freesmartphone.org:aurora Oct 05 19:59:29 freesmartphone.org: 03angelo 07aurora * r6553cdd30197 10/aurora-daemon/src/ (application.cpp virtualkeyboard.cpp): aurora-daemon: several code style fixes Oct 05 21:30:01 gnutoo: ping Oct 06 01:09:50 I was curious of SHR works on both CDMA and GSM versions of the Palm Pre, and if so has the phone and network connection been tested successfully? I could not find definitive information from the freesmartphone project nor SHR. Thanks! **** ENDING LOGGING AT Thu Oct 06 02:59:56 2011