IRC log for #openmoko-cdevel on 20100726

00:00.38*** join/#openmoko-cdevel Q-Master (~qmaster@89-179-64-11.broadband.corbina.ru)
00:26.15*** join/#openmoko-cdevel nslu2-log (~nslu2-log@limax.nslu2-linux.org)
00:28.15*** join/#openmoko-cdevel nslu2-log (~nslu2-log@limax.nslu2-linux.org)
00:59.19*** join/#openmoko-cdevel Zeroedout (zeroedout@xx114200220.cipherkey.com)
01:01.43*** join/#openmoko-cdevel methril (~methril@189.27.128.101.dynamic.adsl.gvt.net.br)
01:05.09*** join/#openmoko-cdevel Defiant (erik@g224068180.adsl.alicedsl.de)
01:44.01*** join/#openmoko-cdevel methril (~methril@189.27.128.101.dynamic.adsl.gvt.net.br)
01:49.11*** join/#openmoko-cdevel zing (~zing@fedora/zing)
01:54.56*** join/#openmoko-cdevel eolson (~eolson@c-24-13-244-61.hsd1.il.comcast.net)
02:06.58*** join/#openmoko-cdevel wolfspraul (~wolfsprau@lucia.q-ag.de)
02:52.42*** join/#openmoko-cdevel Flyser_ (~quassel@p578D182C.dip.t-dialin.net)
04:07.32*** join/#openmoko-cdevel radekp (~radek@88.146.48.30)
04:33.54*** join/#openmoko-cdevel DocScrutinizer (~halley@openmoko/engineers/joerg)
04:48.44*** join/#openmoko-cdevel vanous123 (~vanous@194.228.223.3)
05:00.15*** join/#openmoko-cdevel nslu2-log (~nslu2-log@limax.nslu2-linux.org)
05:01.56*** join/#openmoko-cdevel khoonirobo (~versus@119.82.77.115)
05:29.41*** join/#openmoko-cdevel Zeroedout (zeroedout@xx114200220.cipherkey.com)
05:51.09TAsnhttp://www.geeksphone.com/en/
06:00.00*** join/#openmoko-cdevel gnustavo (ejabberd@galleta.ziritione.org)
06:03.40mrmokuTAsn: hmm... they say to ship limited units... that's neww
06:08.01*** join/#openmoko-cdevel GarthPS (~quassel@vig38-4-82-233-124-245.fbx.proxad.net)
06:13.41mrmokuAinulindale: can't obey to rule #10 :P
06:21.44*** join/#openmoko-cdevel Mwyann (~Mwy@89.86.135.185)
06:26.46*** join/#openmoko-cdevel mzanetti (~mzanetti@46.114.176.225)
06:53.11*** join/#openmoko-cdevel ao2 (~ao2@cl-35.trn-01.it.sixxs.net)
07:13.47*** join/#openmoko-cdevel GarthPS|office (~quassel@LMontsouris-156-25-44-122.w80-13.abo.wanadoo.fr)
07:15.09*** join/#openmoko-cdevel vanous123 (~vanous@robe.ludik.cz)
07:23.50*** join/#openmoko-cdevel GarthPS-onwin (~quassel@LMontsouris-156-25-44-122.w80-13.abo.wanadoo.fr)
07:55.38*** join/#openmoko-cdevel xrmx (~rm@dynamic-adsl-78-14-62-246.clienti.tiscali.it)
07:59.42*** join/#openmoko-cdevel |_0xEF| (~kvirc@62.64.65.186)
08:09.48*** join/#openmoko-cdevel Heinervdm (~thomas@pD9E1646B.dip.t-dialin.net)
08:13.53*** join/#openmoko-cdevel sicu (~sicu@ti0090a380-dhcp0975.bb.online.no)
08:18.11*** join/#openmoko-cdevel GarthPS|office (~quassel@LMontsouris-156-25-44-122.w80-13.abo.wanadoo.fr)
08:24.14*** join/#openmoko-cdevel valos (~valos@2001:7a8:115a:1:219:b9ff:fe63:f3fe)
08:53.51playya_moin
08:54.57*** join/#openmoko-cdevel |_0xEF| (~kvirc@62.64.65.186)
09:28.10*** join/#openmoko-cdevel Meomer (~phaegi@gw.ptr-80-238-173-59.customer.ch.netstream.com)
09:37.58*** join/#openmoko-cdevel magie_01123 (~priyanka@61.12.3.20)
09:38.34magie_01123does android support dvd video playback
09:45.47*** join/#openmoko-cdevel otypoks (~e55c24034@xkh1g1.infr.xiaoka.com)
09:45.58*** part/#openmoko-cdevel otypoks (~e55c24034@xkh1g1.infr.xiaoka.com)
09:46.12*** join/#openmoko-cdevel otypoks (~e55c24034@xkh1g1.infr.xiaoka.com)
09:55.57*** join/#openmoko-cdevel phh (~quassel@2a01:e35:2e4b:b2b0:250:8dff:fee1:c793)
10:08.12*** join/#openmoko-cdevel Martix (~martix@4.177.broadband3.iol.cz)
10:16.19*** join/#openmoko-cdevel beniwtv (~beniwtv@124.Red-83-36-62.staticIP.rima-tde.net)
10:16.49beniwtvHas anyone besides me problems with GSM detaching from the network in latest SHR-U?
10:57.09*** join/#openmoko-cdevel dos1 (~dos@unaffiliated/dos1)
11:08.29*** join/#openmoko-cdevel mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net)
11:12.04*** join/#openmoko-cdevel Q-Master (~qmaster@89-179-64-11.broadband.corbina.ru)
11:15.02mrmokubeniwtv: what revision of fsogsmd has latest SHR-U?
11:15.07mrmokuchecks
11:17.30mrmokubeniwtv: have to build updated cornucopia... can't do that before tonight though
11:17.36mrmokubut then that problem is fixed
11:17.53Q-Masteris tired of WSs
11:18.05mrmokubeniwtv: if you need an urgent fix put 'pin = 1234' into your /etc/phonefsod.conf in the [gsm] section
11:18.16mrmokuQ-Master: WS is gone for me
11:18.31Q-Mastermrmoku: how?
11:18.42mrmokukernel update
11:19.05Q-Masterno shr-u update yet
11:19.17mrmokuit was one of the last kernel updates
11:19.54Q-Masterthe kernel was not updated for a very long time already by opkg update/upgrade in SHR-u
11:20.23mrmokuroot@om-gta02 ~ # opkg list_installed kernel
11:20.24mrmokukernel - 2.6.32.13-oe3.3+gitr6+a9254be10ac2294ea20165a87c09ea6afcf66d94-r0.5
11:20.45Q-Mastermrmoku: yep. this one is at mine neo me also
11:20.57mrmoku|lunchQ-Master: hmm... for me WS is gone with that
11:21.41Q-Mastergot this morning suspend problem. after an alarm wakeup no suspend possible. even autosuspend resumed after a short time.
11:21.59Q-Masterand got a WS just 2 min's ago when touched the display.
11:22.27lindi-Q-Master: what was the resume reason?
11:23.28Q-Masterlindi-: AFAIK as always on new kernel: unknown. no such file or directory.
11:23.48Q-Mastermrmoku|lunch: and LEDs are now not working also. 8(
11:24.07lindi-Q-Master: well can you find the resume_reason files manually?
11:24.39Q-Masterlindi-: the last time i've tried - found none. let me resume and check. 1 sec
11:26.15Q-Masterlindi-: 2010-07-26T11:23:51.310200Z [WARN]  fsousaged : Can't read-open /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-resume.0/resume_reason: No such file or directory                                                                                
11:26.15Q-Master2010-07-26T11:23:51.310927Z [INFO]  LowLevelOpenmoko <>: No resume reason marked in /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-resume.0/resume_reason                                                                                      
11:26.15Q-Master2010-07-26T11:23:51.311698Z [INFO]  UsageController <8 R>: Resume reason seems to be FSO_USAGE_RESUME_REASON_Unknown
11:26.27lindi-Q-Master: find /sys | grep resume
11:26.37Q-Master1 sex
11:26.44Q-Masters/sex/sec
11:27.15*** join/#openmoko-cdevel GarthPS (~quassel@vig38-4-82-233-124-245.fbx.proxad.net)
11:27.38Q-Masterlindi-: /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/resume_reason
11:28.03Q-Masterthe path is wrong
11:28.46*** join/#openmoko-cdevel eolson (~eolson@c-24-13-244-61.hsd1.il.comcast.net)
11:28.56lindi-Q-Master: there should be _two_ resume_reason files
11:29.13Q-Masterlindi-: nop. only 1 here
11:29.21lindi-Q-Master: 2.6.32 bug I guess
11:29.29Q-Mastermight be
11:29.40Q-Masterbut that was from beginning.
11:29.50Q-Masterthere are too much bugs already. 8(
11:29.53lindi-yes I listed it myself too
11:30.23lindi-no report though since I thought it would just be non-implemented feature
11:35.39*** join/#openmoko-cdevel ao2 (~ao2@cl-35.trn-01.it.sixxs.net)
12:07.32dos1Q-Master: LED non working?
12:07.45dos1Q-Master: are you sure you have up-to-date rules.yaml for oeventsd?
12:08.04dos1i have already fixed LEDs some time ago
12:09.00Q-Masterdos1: 1 sec.
12:10.04*** join/#openmoko-cdevel thrashold (~europan@3mhz.net)
12:11.31Q-Masterdos1: I have this one: http://pastebin.org/420208
12:12.17dos1Q-Master: it's old
12:12.34dos1Q-Master: you don't update conf files after opkg upgrade???
12:12.46*** join/#openmoko-cdevel pespin (~pespin@78.pool85-50-74.dynamic.orange.es)
12:13.43Q-Masterdos1: I have only this one. no -opkg files...
12:13.55*** join/#openmoko-cdevel raster (~raster@enlightenment/developer/raster)
12:13.57Q-Masterdos1: what package contains this?
12:14.03dos1strange
12:14.11dos1frameworkd-config-shr
12:14.37*** join/#openmoko-cdevel daniele_athome (~daniele@2a01:608:ffff:3644:21d:7dff:fe91:a28c)
12:14.51daniele_athomehi guys
12:15.01daniele_athomethere's a typo in the ncurses recipe
12:15.09daniele_athome-fforward-progagate
12:36.29Q-Masterdos1: nothing changed.
12:37.05Q-Masterdos1: /etc/freesmartphone/oevents/rules.yaml haven't changed a bit.
12:37.10dos1Q-Master: http://git.shr-project.org/git/?p=shr-themes.git;a=blob;f=frameworkd/frameworkd-config-shr/om-gta02/rules.yaml;h=8f7e2a7a9fc849d816f2ad03b3f32d610bb5fc40;hb=HEAD
13:00.16Gabrysxrmx: hi
13:00.33GabrysI built the QtWebKit, but it segfaults on JavaScript
13:00.52xrmxGabrys, with or without the patch?
13:00.57Gabryswith JIT
13:01.05Gabrysthen I reverted the patch, compiled again
13:01.09Gabrysand it crashes as well
13:01.30GabrysI'm not sure if I cleaned the place in the proper way
13:03.06Gabrysyes, it's badly cleaned
13:03.08xrmxGabrys, this suggests that qt use .pro files and not autotools http://trac.webkit.org/wiki/BuildingQtOnLinux
13:03.12Gabrysthe same md5sum of libQtWebKit.4.9.0
13:03.21*** join/#openmoko-cdevel radekp (~radek@63.120.broadband10.iol.cz)
13:03.28xrmxGabrys, so my patch does not do any difference to your build
13:04.18Gabrysxrmx: ah ok
13:04.28Gabrysxrmx: I'm going to find out which revision works anyway
13:04.41xrmxGabrys, have fun :P
13:05.27GabrysI'm tired of this
13:05.34Gabrysbut what else to do
13:05.37GabrysI need to have this working :-)
13:06.06xrmxGabrys, then use a release instead of svn no?
13:06.37GabrysI need the improvements from QtWebKit2
13:07.07xrmxGabrys, ah!
13:46.26*** join/#openmoko-cdevel TAsn (~tasn@85-250-165-25.bb.netvision.net.il)
14:18.36*** join/#openmoko-cdevel chris38_ (~chris38@freeway.rd.francetelecom.com)
14:21.51*** join/#openmoko-cdevel vanous123 (~vanous@robe.ludik.cz)
14:23.25*** join/#openmoko-cdevel stefan_schmidt (~stefan@2001:638:602:1183:21f:16ff:fe0d:7d41)
14:29.07*** part/#openmoko-cdevel otypoks (~e55c24034@xkh1g1.infr.xiaoka.com)
14:42.58*** join/#openmoko-cdevel xrmx (~rm@dynamic-adsl-78-14-62-246.clienti.tiscali.it)
15:01.46*** join/#openmoko-cdevel sybren (~sybren@ip79-123-210-87.adsl2.static.versatel.nl)
15:01.50sybrenhey folks
15:02.09*** join/#openmoko-cdevel johnsu01 (~user@fsf/staff/johnsu01)
15:03.16sybrenMy SHR-testing dmesg gives me "JFFS2 notice: (50) check_node_data: wrong data CRC in data node at 0x0d263ec0: read 0x4e5f6846, calculated 0x20f14315" - should I start to worry?
15:03.24sybrenI also see "JFFS2 warning: (868) jffs2_sum_write_data: Not enough space for summary, padsize = -900"
15:16.00*** join/#openmoko-cdevel pespin_ (~pespin@78.pool85-50-74.dynamic.orange.es)
15:16.18*** join/#openmoko-cdevel wolfspraul (~wolfsprau@lucia.q-ag.de)
15:25.59*** join/#openmoko-cdevel rohezal (~rohezal@port-92-202-188-122.dynamic.qsc.de)
15:27.30rohezalhi
15:27.44rohezali want to write a small game for the freerunner
15:27.50rohezalusing SDL
15:28.07rohezali want to blit as much as possible.
15:28.59rohezali read that the glamo can blit (via SDL). but only support 512*512 pixel
15:29.06rohezalcan i use 640*480 and use hardware accelerated blitting of the glamo?
15:29.25rohezalor is the 512*512 the maximum texture size and the glamo can blit in larger areas?
15:30.58*** join/#openmoko-cdevel eolson (~eolson@maze.mcs.anl.gov)
15:33.14Weissrohezal: 511x511 is the maximum size of a target buffer for 3D in Glamo
15:33.30Weissyou can blit as much as you like (actually up to 640x640 IIRC)
15:33.38rohezalcool thx guys :)
15:33.54Weissyou could use DRI/DRM for your access to the GPU
15:34.10Weiss(that's what it's for)
15:36.17rohezalim not so deep in gpu stuff
15:36.30rohezalwhen i use SDL_BlitSurface
15:36.38rohezaldoes it use the glamo?
15:36.50rohezalthe main idea is the avoid sending the frame from the cpu to the gpu
15:37.02rohezalbecause the !"&/() 7 MB/s cpu<->gpu bus
15:37.07Weissnot sure actually - maybe it does, via X
15:37.29rohezalhttp://wiki.openmoko.org/wiki/Smedia_Glamo_3362 Glamo's 2D engine is currently used to accelerate solid fills and blits in both XGlamo (Kdrive) and X.org (xf86-video-glamo).
15:37.49rohezalhmmm ok
15:37.53Weissyep, but whether or not your SDL commands make it through SDL to X to EXA in a useful way is a different matter
15:37.53rohezalcan i test it^^
15:38.06rohezalcan i test it?^^
15:38.33Weisssure - do continuous fullscreen 640x480 blits and see how fast it is - if it's accelerated, it'll be >50fps (should be closer to 100fps if everything is working optimally)
15:38.53rohezalhmm ok
15:38.56rohezalthx weiss
15:39.10Weissif it's not accelerated, it'll be down at ~11-12 fps
15:39.52*** join/#openmoko-cdevel playya__ (~playya@unaffiliated/playya)
15:42.56*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@ABordeaux-152-1-46-240.w82-125.abo.wanadoo.fr)
15:45.06*** join/#openmoko-cdevel ThibG (~ThibG@81-64-12-99.rev.numericable.fr)
15:48.19rohezalk on my pc my code gets 486.5 FPS
15:48.23rohezallet try on freerunner
15:48.36Weissit won't be that high, for sure :)
16:02.48rohezaldo you know if qtopia (with QX) is using a normal x server with hardware acceleration for blitting?
16:03.15Weissdon't think so, but I don't know much about qtopia
16:05.01rohezalhmm gamerunner^^?
16:05.14rohezali got the distro on a sd card
16:09.29*** join/#openmoko-cdevel [HtR]_0xEF^3 (~HtR]_0xEF@62.64.65.186)
16:13.28*** join/#openmoko-cdevel pespin (~pespin@78.pool85-50-74.dynamic.orange.es)
16:15.20*** join/#openmoko-cdevel naeg (~naeg@194.208.239.170)
16:15.48gena2xrohezal: Driver          "Xglamo"
16:16.00gena2xrohezal: in QX.
16:16.47rohezalcool thx @ gena2x
16:23.36*** join/#openmoko-cdevel VDVsx (~Valerio@Maemo/community/contributor/VDVsx)
16:25.03*** join/#openmoko-cdevel max_posedon (~max_posed@80.249.84.73)
16:30.10rohezalfu*k cross compiling
16:30.27rohezal(just want to say it :P)
16:30.49gena2xtame it.
16:31.18Weisshehe
16:31.32Weissagrees that cross-compiling is indeed an absolute pain
16:31.41*** join/#openmoko-cdevel naeg (~naeg@194.208.239.170)
16:31.55Weiss(http://warmcat.com/_wp/2010/02/08/fosdem-and-the-linux-cross-niche/)
16:32.39*** join/#openmoko-cdevel mzanetti (~mzanetti@92.117.51.251)
16:33.12gena2xdisagree. 'absolute pain' is subjective. in fact sdram memory diagram fall to this category.
16:33.41Weisshehe, indeed
16:34.38rohezalworking
16:34.42rohezala bit make file hacking
16:34.51rohezalhmm ok lets get it to the freerunner
16:35.04*** join/#openmoko-cdevel vanous123 (~vanous@194.228.223.3)
16:36.48Weisscompiling stuff natively on the FR takes the same amount of time, but you get to read a book instead of stressing out
16:37.34gena2xi call this 'interrupt driven development'.
16:39.13gena2xyou start thing 1, wait for compilation, start thing 2, then interrupt thing 2, to see why compilation fail on 1. then restart 1, and resume 2. you end up in both 1 and 2 not finished, as you can't concentrate neither.
16:39.42gena2xs/neither/ on any of 1 or 2/
16:40.26Weisseither way takes a long time, however
16:40.37rohezalyes
16:40.44rohezal<- needs an arm cpu desktop
16:40.55rohezalhmmm snap dragon or omap4? ^^
16:41.25*** join/#openmoko-cdevel GarthPS (~quassel@vig38-4-82-233-124-245.fbx.proxad.net)
16:44.11ThibGhm, reminds me there was some ARM-based tablet/laptop... can't remember its name
16:46.44*** join/#openmoko-cdevel mickey| (~mickey@e180129095.adsl.alicedsl.de)
16:47.08misctouchbook
16:47.08miscpeople from  french enlightenment association had one at RMLL, they were our neighboor on the association village
16:47.55ThibGyes, that thing
16:49.03ThibGmisc, did you get to play with it?
16:49.39*** join/#openmoko-cdevel stefan_schmidt (~stefan@p5B0331FD.dip.t-dialin.net)
16:49.55GNUtoo|laptopmickey|,
16:49.57GNUtoo|laptophi
16:50.01GNUtoo|laptopwe must talk privately
16:50.29GNUtoo|laptopabout the next target
16:51.42miscThibG: i just took a look, but you should ask directly on the channel of the french association
16:52.18miscThibG: not sure if this #e.fr
16:52.24ThibGok
16:52.56misc( ask puppet_master about it )
16:56.17rohezalhmmm
16:56.22rohezaldamn seg fault on free runner
16:57.00rohezalsomeone want to look @ the makifle? http://pastebin.de/8556
16:57.21ThibGmisc, the device looks interesting, and not that expensive :)
16:57.50rohezalworking
16:57.53rohezalok damn
16:58.03rohezal12 FPS via blitting in SDL with QT
16:58.18rohezalsomeone knows if there is a distro
16:58.24rohezalwhich supports blitting via SDL?
17:01.20Weisswhich supports *accelerated* blitting via SDL, I guess you mean..?
17:01.30rohezalyes^^
17:01.33rohezalof course
17:01.47rohezalmaybe gamerunner or shr?
17:02.27Weissit depends more on SDL I think, and that will most likely be the same for all
17:02.48Weissmaybe SDL can be configured to use X commands (which X can accelerate) - maybe it's doing something else right now
17:04.58mickey|GNUtoo|laptop: ok, not now, but i'll ping you later
17:07.56*** part/#openmoko-cdevel sybren (~sybren@ip79-123-210-87.adsl2.static.versatel.nl)
17:11.31leviathanGNUtoo|laptop: hmm, it seems snapdragon is also supported by upstream now
17:11.42GNUtoo|laptopnice
17:12.19leviathan1GHz should be enough
17:12.37leviathaneven for ooffice and abiword
17:12.44leviathanrunning fluently
17:13.16rohezalWeiss you know how to force SDL using X commands?
17:13.40rohezalor an other to blit easily for a game without using the X Server directly?
17:17.33leviathantoshiba seems to have produced a nice snapdragon thing
17:17.35leviathanhmm
17:17.41Weissrohezal: to the first: not at all. to the second: I can show you how to send hardware command sequences for a blit. it's tricky, but it'll give you the maximum possible performance (and also render your code specific to FR unless you write some kind of intermediate library)
17:18.29rohezalWeiss: this would be nice. i read the X11 cant use blitting with hardware acceleration at all. DAMN
17:19.32Weisswherever did you read that?
17:19.41Weissor do you mean SDL+X11 can't use accel?
17:20.33rohezalhttp://kevinlocke.name/inquiry/sdlblitspeed/sdlblitspeed.php
17:20.36rohezalSDL supports hardware accelerated blitting of ``normal'' surfaces to the
17:20.36rohezalscreen surface. However, this mode is not supported for X11 (except for
17:20.37rohezalsome cards when using DGA). In fact, the only backend hardware
17:20.37rohezalaccelerated memory-to-screen blitting is well supported seems to be the
17:20.37rohezalDirectX5 backend for Windows.
17:20.42rohezalhttp://forums.libsdl.org/viewtopic.php?p=4943&sid=2414d7b2c07c79f5f9c8e41a12e55d8a
17:21.01rohezalmaybe im misunderstand some things
17:21.28leviathanGNUtoo|laptop: http://htc-linux.org/wiki/index.php?title=Tg01
17:21.48leviathanGNUtoo|laptop: http://en.wikipedia.org/wiki/Toshiba_TG01
17:21.55leviathanGNUtoo|laptop: snapdragon
17:21.58leviathan:-D
17:21.59GNUtoo|laptopok
17:22.02Weissrohezal: ok, so that's just SDL.  X11 can accelerate things for sure..
17:22.08leviathanbut first we make htcdream run properly
17:22.23rohezalWeiss: sachmal du sprichst deutsch oder? so vom namen her?^^
17:22.40GNUtoo|laptopleviathan, yes and?
17:22.46GNUtoo|laptopleviathan, you plan to buy one?
17:23.01rohezalWeiss: yes i know. but it looks like sdl cant use accelerated blitting with x
17:23.02leviathanrohezal: openmoko-de
17:23.08GNUtoo|laptopfor the dream I have the ability to recruit a new developer
17:23.09leviathanrohezal: ;-)
17:23.25leviathanGNUtoo|laptop: wonderfull!
17:23.26GNUtoo|laptoplet's see how it goes
17:23.38GNUtoo|laptopleviathan, the only problem is that he lacks the hardware
17:23.39leviathanGNUtoo|laptop: we can always use new devs ^_^
17:23.45rohezalleviathan: yes but weiss is in the chanel? why change to de?
17:23.45GNUtoo|laptopleviathan, but I can solve that
17:24.11GNUtoo|laptopleviathan, I know his capabilities and he's trusted
17:24.20GNUtoo|laptopso maybe
17:24.23GNUtoo|laptopI give him my dream
17:24.26leviathanrohezal: here is english given as language, daher für deutsch konversation bitte den deutschen channel ;-)
17:24.30GNUtoo|laptopand get mickey's dream
17:24.39GNUtoo|laptopor something like that
17:24.51Weisshehe
17:25.01GNUtoo|laptopanyway I must finish dream soon
17:25.06GNUtoo|laptopbefore starting a new target
17:25.10leviathanGNUtoo|laptop: yes
17:25.18rohezalleviathan: wait, i though writing the first name with double dots is only visible to the user with that name... damn im an irc noob ... sory
17:25.20leviathanGNUtoo|laptop: I dunno how the meeting will go
17:25.37leviathanrohezal: np
17:25.49GNUtoo|laptopok
17:26.07leviathanrohezal: so, join the german channel
17:26.17leviathanrohezal: you will see me there too ^_^
17:27.19leviathanGNUtoo|laptop: I hope they will buy it... The idea of getting the development done by some people for free should be a hammer argument
17:28.04leviathanGNUtoo|laptop: they give us a platform, we can develop on, with theire cooperation
17:28.05GNUtoo|laptopok
17:28.18GNUtoo|laptopleviathan, can I PM you?
17:28.25leviathanGNUtoo|laptop: of course
17:33.47*** join/#openmoko-cdevel Kryczek (kryczek@chillin.with.the.airconexperts.com)
17:33.47*** join/#openmoko-cdevel Kryczek (kryczek@about/security/staff/Kryczek)
17:33.51*** join/#openmoko-cdevel wolfspra1l (~wolfsprau@lucia.q-ag.de)
17:34.23rohezalok weiss you said there is a way to use hw accelerated blitting. do you know some good links? is it possible to store the images at the gpu ram so it doesnt need to get the images via the cpu for every frame?
17:37.05*** join/#openmoko-cdevel mickey|zzZZzz (~mickey@openmoko/coreteam/mickey)
17:37.12Weissrohezal: sure, here are the demo programs: http://git.bitwiz.org.uk/?p=glamo-dri-tests.git;a=tree
17:37.12mickeylGNUtoo|laptop: ok, i'm here for a bit now
17:37.27GNUtoo|laptopmickeyl, ok
17:37.30Weissthis is the best example: http://git.bitwiz.org.uk/?p=glamo-dri-tests.git;a=blob;f=gdrm-waitq.c;h=159db7dbb9922b039aa3803495a2f5aed67dde45;hb=HEAD
17:37.57Weiss(although, that doesn't use X)
17:39.36rohezalok you are using some headers
17:39.38rohezal<PROTECTED>
17:39.38rohezal<PROTECTED>
17:39.38rohezal<PROTECTED>
17:39.38rohezal<PROTECTED>
17:39.53rohezalwhere can i get them? are you linking against a special lib?
17:41.44Weissrohezal: yep, libdrm..
17:41.57Weissrohezal: but hold on.. are you trying to run within X, or QtE/Qtopia?
17:44.27rohezalX
17:44.37rohezalqtopia can run X Applications
17:44.40rohezalvia QX
17:44.47rohezalits seems to a normal X Server
17:44.49rohezali hope^^
17:45.11WeissI don't think it is.. I think it's more of an X protocol->Qt stuff translator
17:45.28rohezaldo you know gamerunner?
17:45.33rohezalthe distro
17:45.38rohezali got it on a sd card
17:45.45rohezalit uses X
17:45.52rohezalmaybe its worth a try
17:45.54WeissXglamo?
17:45.58rohezalhmmm
17:45.59rohezaldamn
17:46.00Weissthat doesn't have any of this acceleration stuff
17:46.01rohezaldont know
17:46.11rohezalwhat distro would you recommend
17:46.12rohezal?
17:46.16WeissSHR :)
17:46.23rohezalto slow for daily use :(
17:46.48rohezalhope a stable release with a none debug kernel will released in the near future^^
17:47.27rohezallol i googlet for QX... second hit: QX Gay UK Scene Magazine London England - Home-Index
17:47.27rohezal<PROTECTED>
17:47.50Weissthere are only two ways to get acceleration from a user app: [1] program Glamo yourself: old-style, likely to break, difficult, only one thing can use the hardware at once (and if your X server/other display system is already using it and doesn't want to share, you're stuffed). [2] use DRI - which is designed to allow apps to get access to the hardware like this while sharing with other apps and the display system
17:49.12rohezalok so DRI looks good. will it work with QX?
17:49.55rohezalwhere can I learn to programm with DRI? I know a bit about OpenGL and SDL. And a lot about raytracing (witch is quite useless on a freerunner :P)
17:49.57gena2xwait, wait. why indirect rendering can't be accelerated???
17:50.16*** join/#openmoko-cdevel mzanetti (~mzanetti@92.117.218.221)
17:51.36rohezal@ gena2x: indirect rendering means you must render the whole image on the cpu and put it over the slow 7MB/s bus the gpu or? this is what i want to avoid with blitting
17:52.07gena2xno.
17:52.20gena2xand 1st - where is no 7mb/s bus.
17:52.23miscwatch as gena2x is going to explain the bus is faster
17:52.41rohezalohhh is it faster?
17:52.54gena2xrohezal: about bus: http://lists.openmoko.org/pipermail/community/2010-July/062495.html
17:53.08gena2xrohezal: and http://lists.openmoko.org/pipermail/community/2010-July/062504.html
17:54.12rohezalcool thx 4 links
17:56.05gena2xand about direct/indirect rendering: i thought that 'direct' is then application controls hw 'directly', and indirect rendering then hw controlled by X. both can be accelerated.
17:56.19gena2xso both are fast.
17:56.33gena2xof course, only weiss know how this can be applied to glamo :)
17:57.22gena2xbut aiglx is exaple of accelerated indirect rendering...
17:57.50gena2xbrr.
17:58.14gena2xi don't really understand this very good.
17:58.19rohezalhmm ok
17:58.22rohezallooks cool
17:58.27rohezal14 or even 23 mb
17:58.31rohezalbus speed
17:58.41rohezalthere are some changed settings mentioned
17:58.44rohezalwhat settings?
17:59.00ChristWWait cycles.
17:59.28gena2xdo you wish details?
17:59.42gena2xsee patch (in same dir with u-boot)
17:59.51gena2xand s3c manual.
18:00.17gena2xask if in doubt after that.
18:00.22rohezalon a normal pc you can change it via bios
18:00.30rohezalits row latency and col latency or?
18:00.43gena2xglamo is not 'sdram'.
18:00.53gena2xit connected via 'sram' interface.
18:01.08gena2xdiffirent (and simplier) timings used in sram.
18:01.14*** join/#openmoko-cdevel mzanetti (~mzanetti@92.117.2.51)
18:01.18rohezalwait wait waitr
18:01.22gena2xs/diffirent/different/
18:01.41rohezalthe GPU is connect via a sdram interface? why?
18:01.51gena2xwhy not :)
18:02.09gena2xit's not 'sdram interface' its 'memory bus'.
18:02.15gena2xor something like this.
18:02.19rohezalok
18:02.24rohezaland we can change the timings
18:02.29rohezalso more data can be passed
18:02.30gena2xsure.
18:02.39rohezallike normal sd ram rimings
18:02.41rohezaltimings
18:02.48gena2xmy letter is about 2 things.
18:02.57gena2xfirst - it's already not 7Mb/s.
18:03.04rohezalok
18:03.06rohezalunderstand
18:03.19gena2xsecond - it can be even more if timing set more properly.
18:04.03gena2xnew settings were set not after guess, but after checking glamo docs by weiss (and my initial testing).
18:04.37gena2xone problem still exist - according to docs it should be 1-4-2, but this simply not working.
18:05.04gena2xand i've tired to test it - one wrong setting and i have to restore sd from backup :)
18:05.38rohezalahh ok
18:05.49rohezalgood but i still want to learn how to blit^^
18:05.56rohezalwith the glamo :)
18:06.07rohezali need libdrm for it
18:06.09rohezaland the headers
18:06.16gena2xi don't understand, is uses x blit operation is not accelerated?
18:06.24gena2xs/uses/usual/
18:06.28rohezalSDL cant use the X blit operation
18:06.30rohezali think
18:06.35gena2xWeiss: ? ^
18:06.41*** join/#openmoko-cdevel net_tux (~jfthomps@treebeard.csc.ncsu.edu)
18:06.59rohezali just put a baseball via blitting over a 640*480 field
18:07.14rohezalwhich is blitted by one 32*32 plant image
18:07.23rohezalaround 400-500 images
18:07.29rohezalon my desktop
18:07.33rohezal12 on freerunner
18:07.42radekprohezal: QX is just little program that launches regular X server and bypasses all Qtopia redrawing - so that they dont clash
18:07.42rohezalwith HW blitting it should be around 50-100 fos
18:07.43rohezalfps
18:07.59rohezalradekp: what is clash?
18:08.18radekprohezal: so that qtopia and xserver dont draw at the same time
18:08.19gena2xalso keep in mind that glamo internally is not instant too :)
18:08.46rohezalradekp: lol clash... sorry im not a native english speaker
18:08.55radekprohezal: np, me too :)
18:09.24rohezalwell im running the programm since 15 minutes or something
18:09.27rohezal12 fps :(
18:09.57gena2xyou can compare with x via framebuffer.
18:10.05gena2xwhich is not accelerated for sure :)
18:10.14rohezal*g*
18:10.31rohezalweiss said above i can use accelerated blitting via DRM / DRI with libdrm
18:10.42rohezaldo you know how to get it and the header files for it?
18:11.14gena2xonly weiss knows such things...
18:14.28radekpmaybe after upgrade to debian sid you can install libdrm dev packages, but i have never tried
18:14.30rohezalhmm ok^^
18:15.11radekpor you can try build from sources
18:16.16ChristWI've bumped my head into this error a few times over the last couple of days, and make update && make build doesn't make it go away: http://pastebin.com/gAbiP9Yh
18:16.28ChristW(I'm trying to build SHR-U)
18:17.42rohezalohh its on the freerunner... maybe i can just copy it to the pc for cross compiling
18:17.49rohezalbut i still need the headers
18:17.50*** join/#openmoko-cdevel valos (~valos@mar92-6-82-227-150-198.fbx.proxad.net)
18:19.41gena2xalways thought that all this 'dri' 'drm' is for gl... and normal blit acceleration is EXA or XAA...
18:21.54rohezali dont know
18:25.02rohezalhmm ok
18:25.13rohezalopkg-target install libdrm-dev
18:25.42*** join/#openmoko-cdevel mwester (~mwester@nslu2-linux/mwester)
18:26.39rohezalbut no header files
18:26.49rohezaldont tell me i have to sign this dna to get it
18:27.44Weissrohezal: so... direct and indirect rendering are distinct from accelerated/non-accelerated
18:27.53*** join/#openmoko-cdevel pb__ (~pb@blundell.swaffham-prior.co.uk)
18:28.34Weissyou can have accelerated direct rendering (that's DRI), accelerated indirect (that's AIGLX), but you can also have unaccelerated direct (that's "swrast_dri.so"), and of course non-accelerated indirect (version 0.0.1 GLX)
18:29.22gena2xbut hm... all this is gl-related.
18:29.28rohezalok... im ok with both unaccelerated (when AIGLX is supporting what is needed)
18:29.50rohezalbut your sample is using some headers files. how can i get them?
18:30.00rohezal#include "drm.h"
18:30.00rohezal#include "glamo_drm.h"
18:30.00rohezal#include "drmtest.h"
18:30.00rohezal#include "glamo-regs.h"
18:30.08*** join/#openmoko-cdevel mzanetti (~mzanetti@92.117.2.51)
18:30.56rohezal./local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/include/drm/drm.h
18:30.58rohezalis there
18:31.01rohezalbut the other files not
18:31.20Weissgena2x: yep, it is. but "direct/indirect" has little to no meaning outside GLX
18:31.53gena2xso, to have accelereated blit, we have to have XAA.
18:33.10rohezalWeiss: but you mentioned this code: http://www.mail-archive.com/devel@lists.openmoko.org/msg06145.html
18:33.15rohezalfor blitting
18:34.09Weissgena2x: or EXA, or KAA, but all of those are just ways for the X server to tell the X driver what it wants to happen, not ways for the app to tell X what it wants
18:36.16rohezalWeiss: its for DRI or? is there a tutorial how to do it? There are some header files i cant find on my system. How can I get them?
18:41.55gena2xWeiss: got it. so some other way other than Xlib exists to control X server (for 2d)?
18:51.15*** join/#openmoko-cdevel ruoso (~ruoso@187.79.41.11)
18:53.58rohezal...
18:54.21rohezalguys need i get the source with GIT from the http://git.bitwiz.org.uk/?p=libdrm.git;a=shortlog;h=refs/heads/glamo ?
18:54.30rohezalneed i to build libdrm myself?
18:54.40rohezalare there the headers for the drm lib?
18:55.15rohezalwhat is the login for git to check the source out?
18:55.27gena2xahh... ok, i got it "The main consumer of this extension will be a direct rendering OpenGL
18:55.27gena2xdriver, but the DRI2 extension is not designed to be OpenGL specific.
18:55.27gena2xDirect rendering implementations of OpenVG, Xv, cairo and other
18:55.27gena2xgraphics APIs should find the functionality exposed by this extension
18:55.27gena2xhelpful and hopefully sufficient.
18:55.28gena2x"
18:55.38gena2xwill be silent forever on this topic.
18:56.00gena2xthinks it's a bit overcomplicated.
18:56.30gena2xgone to do something more useful :)
18:56.38rohezalhi gena2x
18:56.47rohezaldo you know where to obtain the headers?
18:56.50rohezallast try
18:56.55rohezal^^
18:57.40*** join/#openmoko-cdevel PaulFertser (~PaulFerts@aein-1-pt.tunnel.tserv6.fra1.ipv6.he.net)
18:58.19rohezal...
18:58.20rohezalhttp://git.bitwiz.org.uk/?p=libdrm.git;a=snapshot;h=HEAD;sf=tgz
18:58.22rohezalsry guys
18:58.25rohezal<- stupid :(
19:00.24*** join/#openmoko-cdevel roh (~roh@yamato.hyte.de)
19:04.23*** join/#openmoko-cdevel vanous123 (~vanous@194.228.223.3)
19:07.35rohezalchecking for PTHREADSTUBS... configure: error: Package requirements (pthread-stubs) were not met:
19:07.35rohezalNo package 'pthread-stubs' found
19:07.36rohezalConsider adjusting the PKG_CONFIG_PATH environment variable if you
19:07.36rohezalinstalled software in a non-standard prefix.
19:07.36rohezalAlternatively, you may set the environment variables PTHREADSTUBS_CFLAGS
19:07.36rohezaland PTHREADSTUBS_LIBS to avoid the need to call pkg-config.
19:07.38rohezalSee the pkg-config man page for more details.
19:07.40rohezalFATAL: oe_runconf failed
19:08.21*** join/#openmoko-cdevel fsteinel (~fsteinel@fedora/fsteinel)
19:08.54rohezalom-conf libdrm
19:09.37*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@95.232.142.62)
19:12.02*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@95.232.142.62)
19:20.00*** join/#openmoko-cdevel dvermd (~david@ijo32-1-78-234-93-192.fbx.proxad.net)
19:22.25*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@95.232.142.62)
19:30.24*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@95.232.142.62)
19:38.16*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@95.232.142.62)
19:40.40*** join/#openmoko-cdevel gena2x (~gena2x@bsdmn.com)
19:46.23*** join/#openmoko-cdevel AndreasD (~andreas@1407ds1-ns.0.fullrate.dk)
19:50.16ThibGWeiss, beware of new Cowon firmwares...
19:51.24ThibGI don't know for your model, but latest S9 upgrade ignores vorbis comments... completly... it's not even the ARTISTSORT thing
19:52.21*** part/#openmoko-cdevel gnustavo (ejabberd@galleta.ziritione.org)
19:53.09*** join/#openmoko-cdevel eolson (~eolson@mcswl160.mcs.anl.gov)
19:53.53WeissThibG: ick :S
19:54.04WeissThibG: my X5 is quite old.. was thinking of upgrading
19:54.23ThibGfortunately, I can revert to the previous firmware, and it works great
19:55.39CIA-61freesmartphone.org: 03morphis 07msmcomm * rf12688f7943e 10/msmcommd/src/lowlevelcontrol.vala: msmcommd: initialize string array before using it
19:55.40CIA-61freesmartphone.org: 03morphis 07msmcomm * r21393bcecbc2 10/msmcommd/src/ (remoteclient.vala remoteclienthandler.vala): msmcommd: disconnect the client the right way
19:55.41CIA-61freesmartphone.org: 03morphis 07msmcomm * r3b0d8780f69c 10/libmsmcomm/ (5 files in 3 dirs): libmsmcomm: implement ref id for test_alive msg/resp
19:55.59ThibGmy concern is more about headphones, now...
19:56.42*** join/#openmoko-cdevel gnutoo (~gnutoo@95.232.142.62)
19:57.15ThibGmines are dead, and the advertised life-time warranty is a real challenge here
19:58.23Weisson the headphones?
19:58.38ThibGyes (not Cowon's)
19:58.40WeissI never used the ones which came with it
19:58.42Weissah
19:58.48ThibGKoss :)
20:00.22ThibGthe headphones that comes with Cowon's players are crap...
20:00.43ThibGthat said, I've just seen they are selling some other headphones now
20:02.45*** join/#openmoko-cdevel Orias_Korva (~atilla@188.58.98.220)
20:05.42*** join/#openmoko-cdevel dvermd (~david@ijo32-1-78-234-93-192.fbx.proxad.net)
20:08.18*** join/#openmoko-cdevel GNUtoo|laptop (~gnutoo@95.232.142.62)
20:16.25*** join/#openmoko-cdevel \marco (~marco@dynamic-adsl-78-12-224-73.clienti.tiscali.it)
20:16.31\marcohi to all
20:16.48\marcoI've a very strange problem with the FR and a thomson router
20:17.34\marcousing iliwi it result successful connected
20:18.06\marcobut I can't ping the router or the internet
20:18.34lindi-\marco: wlan? wpa?
20:18.39\marcoinspecting with wireshark I've found that the FR don't answer to the router arp request
20:18.58\marcolindi-: wlan with wpa
20:19.06lindi-\marco: uname -r? maxperf?
20:19.20\marcoI've tried maxperf, same result
20:19.52\marcothe kernel is the last but the problem always exist from the first kernel I've used
20:20.39\marcoIf i ping another pc connected in wifi it ping! and FR correctly answer to arp request
20:20.47lindi-\marco: where did you run wireshark?
20:20.54\marcofrom another pc
20:21.06lindi-\marco: how can it see ARP traffic?
20:21.24lindi-ah, it's in the same LAN as the wlan AP?
20:21.25\marcowell.. i mean the arp broadcast
20:21.36\marcoyes
20:22.31\marcothe router ask for the mac addres of the ip 192.168.1.67 ( the FR )  but there's no answer from the FR
20:22.44lindi-\marco: sniff the traffic on FR. does it see that request?
20:23.08\marcomhm I've to install wireshar on the FR
20:23.14\marco*wireshark
20:23.14lindi-\marco: just install tcpdump
20:23.19\marcook
20:23.33lindi-\marco: you can load it to wireshark then
20:23.41\marcooh good
20:24.18\marcojust a moment ( I'm not at home and I've to to take the networking from this pc via usb )
20:27.19\marcook installing tcpdump
20:30.34alexxyhi all!
20:30.52*** join/#openmoko-cdevel ferluszt (~peter@p5DD28EBE.dip0.t-ipconnect.de)
20:31.04alexxymrmoku: TAsn: seems vibro is br0ken again in latest shr-u
20:32.46\marcolindi-: mhm.. tcpdump on FR says the FR is answering to the arp request
20:33.21GNUtoo|laptophi mickeyl
20:34.17\marcolindi-: another thing, ifconfig eth0 on the FR report broadcast 0.0.0.0 but changing it with an ifconfig eth0 .. (etc) doesn't solve the problem
20:36.25\marcoany idea?
20:37.36leviathanmrmoku: hi
20:40.48\marcoin the FR ARP reply, tcpdump say (oui unknown). Is it norma?
20:41.07\marco*normal
20:42.07lindi-\marco: if you can install "ip" command then output of iki.fi/lindi/print-net-settings would be interesting. ifconfig is really not very debug-friendly
20:48.07\marcoeheh ok. opkg install iproute2 in progress
20:50.23lindi-\marco: however, if it answers the arp request correctly then I don't think there is much we can do
20:50.52\marcosigh :(
20:50.58mrmokuleviathan: hey
20:51.06lindi-\marco: try without wpa
20:51.12\marcohowever the router seems to not receive the arp reply
20:51.15GNUtoo|laptophi
20:51.21GNUtoo|laptopwho was the person who bought a nexusone?
20:51.38\marcolindi-: ok! oh, I've installed iproute2 which "debug" you suggest?
20:51.47GNUtoo|laptopmickeyl, do you remember who got nexusone?
20:51.59mrmokuGNUtoo|laptop: Deubeuliou has one
20:52.10lindi-\marco: iki.fi/lindi/print-net-settings should print all relevant info
20:52.14GNUtoo|laptopok thanks
20:52.16GNUtoo|laptophi Deubeuliou
20:52.19Deubeuliouhi
20:52.21mickeylKensan as well
20:52.25GNUtoo|laptopok
20:52.27Deubeuliouyeah, sorry, I didn't send a feedback :/
20:52.38GNUtoo|laptopDeubeuliou, I've many possibilities
20:53.00GNUtoo|laptoproughly or get a free nexusone or buy a n900 which isn't cheap
20:53.09mrmokumickeyl: did you read my messages in backlog?
20:53.15Deubeuliou(and since my vacation are beginning shortly, I won't be able to for a moment)
20:53.19mrmokumickeyl: and congrats for the new car :)
20:53.22\marcolindi-: mhm : 404 Not Found
20:53.27DeubeuliouGNUtoo|laptop: why can't you get both ?
20:53.40GNUtoo|laptopDeubeuliou, that would be counter-productive
20:53.46Deubeuliouif the nexusone is free, that shouldn't be a problem
20:53.48DeubeuliouI see
20:53.51\marcooops
20:53.54\marcomy fault sorry
20:53.54GNUtoo|laptopI have limited time
20:54.04mrmoku~lart limited time
20:54.04aptbrandishes Excalibur! "With this sword, I vanquish thee, limited time!" and lops off limited time's head
20:54.05\marcolindi-: it works sorry ^_^
20:54.05GNUtoo|laptopif I don't use nexusone why getting it?
20:54.32\marcolindi-: let me see what the script says
20:55.02Deubeuliouyou could donate it to someone that wants to hack on it but can't afford one. (but that's maybe off-topic)
20:55.10mickeylmrmoku: thanks :). +CFUN=4 and +CFUN=1 does not correctly work w/ the states?
20:55.32GNUtoo|laptopok
20:55.44GNUtoo|laptopDeubeuliou, to get it I'll have to do some minor replicant work
20:55.52GNUtoo|laptopDeubeuliou, so now to the point...
20:55.54DeubeuliouGNUtoo|laptop: I heard the openess of the n900 was not so big ?
20:55.59GNUtoo|laptopwhat works,what doesn't
20:56.01Deubeuliouok
20:56.06GNUtoo|laptopDeubeuliou, n900 has battery decoded
20:56.18GNUtoo|laptopDeubeuliou, you can also talk to the bootloader with free software
20:56.20mrmokumickeyl: that was one... the other one that re-requesting works
20:56.26GNUtoo|laptopDeubeuliou, and....the kenrel is a good state
20:56.29Deubeuliouok
20:56.41mrmokumickeyl: and that there is open stuff in meego for gsm audio routing on n900
20:56.48GNUtoo|laptopDeubeuliou, and....ophono has some sort of (incomplete) support for n900
20:56.50Deubeuliouthe big problem with the nexus one, imho, is the kernel, actually
20:56.52*** join/#openmoko-cdevel eolson (~eolson@maze.mcs.anl.gov)
20:57.00mickeylmrmoku: ok. i'll have a look at the cfun issue
20:57.06mickeylmrmoku: ah, that's good news
20:57.26mrmokuyup
20:57.32Deubeuliouthere are a lot of problem with module dependencies in the kernel at android.kernel.org
20:57.54mrmokumickeyl: it consists of a lib and a gstreamer module
20:58.09mickeylmrmoku: nice, and both is open?
20:58.12\marcolindi-: indeed, "ip" show the correct broadcast ip for eth0
20:58.13mrmokuyup
20:58.15leviathanmrmoku: ah, youre on
20:58.16mickeylexcellent
20:58.18leviathanwonderful
20:58.19leviathan^^
20:58.22DeubeuliouI don't know what is the state of the porting of the driver into a vanillia kernel
20:58.33leviathanPerhaps you've an idea, why the following thing happens
20:58.39leviathanI made a recipe for maxima
20:58.57leviathanbasically it should produce arm code, when I inherit autotools
20:59.05mrmokumickeyl: http://meego.gitorious.org/meego-cellular/libcmtspeechdata
20:59.15leviathanmrmoku: but its always producing code for the buildhost
20:59.16\marcolindi-: I'll try without wpa :) thanks however ^^
20:59.38GNUtoo|laptopDeubeuliou, forget about vanilla
20:59.44mrmokuand http://meego.gitorious.org/maemo-multimedia/pulseaudio-modules-meego
20:59.48GNUtoo|laptopDeubeuliou, that'll be done but it'll take too much time
20:59.52DeubeuliouGNUtoo|laptop: I also read that the audio could cause problems
21:00.01GNUtoo|laptopDeubeuliou, you didn't try alsa?
21:00.04GNUtoo|laptopwhat did you try?
21:00.07leviathanmrmoku: http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=40abfa09ae5dc3310888576756b94e3e42e6b5ce
21:00.08DeubeuliouI don't remember
21:00.33leviathanmrmoku: it ignores the configure and produces no arm code
21:00.47leviathanmrmoku: it builds for x86 no mater what I do
21:00.55mickeylmrmoku: heh, i guess we're going to have fun with PA again then :D
21:01.07mickeylnot that it is bad, it just performed lousy...
21:01.09mrmokuleviathan: do you have CPATH set in your env?
21:01.11mrmokumickeyl: hehe, yes
21:01.19leviathanmrmoku: CPATH?
21:01.44leviathanmrmoku: why?
21:01.45DeubeuliouGNUtoo|laptop: ah, and the touchscreen is a little weird
21:01.52leviathanmrmoku: and where shall it point to?
21:02.04mrmokuleviathan: or LIBRARY_PATH
21:02.07mrmokuleviathan: must be unset
21:02.10GNUtoo|laptopDeubeuliou, that should be easy to change touchscreen
21:02.13leviathanahh, ok
21:02.23GNUtoo|laptopDeubeuliou, so basically you didn't make a lot of progress? lack of time?
21:02.28mrmokuleviathan: I had some problem like that due to having that in my env
21:02.33Deubeuliouthe bottom part of it actually are the four touch-buttons
21:02.41leviathanmrmoku: I don't have any of them set
21:02.42\marcoI've to go.. bye! :)
21:02.48DeubeuliouI don't know if I'm clear ...
21:02.54mrmokumickeyl: but omap has some kind of fp, no?
21:02.59mrmokuthat was the main problem I think
21:03.29GNUtoo|laptopDeubeuliou, ahh ok like palm pre?
21:03.31mrmokubuilding from scratch again on buildhost :/
21:03.32Deubeuliouthe four buttons at the bottom are part of the touchscreen
21:04.22DeubeuliouI don't know the palm pre
21:04.22GNUtoo|laptopDeubeuliou, I understand...palm pre is a bit like that
21:04.22GNUtoo|laptopthe touchscreen goes over the screen
21:04.22GNUtoo|laptopthe "over the screen part"
21:04.22GNUtoo|laptopis a gesture area
21:04.22mickeylmrmoku: yes, but they also have some nice additional instructions which e.g. palm used to _massively_ speed up the pulseaudio resampler (which basically was the actual CPU hog on the FR)
21:04.32mickeylmrmoku: we can perhaps reuse those patches as well
21:04.39GNUtoo|laptopDeubeuliou, maybe you should report your findings to:
21:04.59GNUtoo|laptophttp://wiki.freesmartphone.org/index.php/HardwareComparison
21:06.44Deubeuliouapart from that ; I don't know how to make the compass work, neither the camera
21:08.36mickeylroughly same situation as the dream then
21:09.03DeubeuliouI got to go. I the first days of August, I'll have some time to check more things
21:09.13GNUtoo|laptopok
21:09.17GNUtoo|laptopme too I got to go
21:09.22leviathanmrmoku: hmm, it doesnt seem to be that, none of this environement variables is set
21:09.24leviathanhmm
21:09.35Deubeuliouwhat takes me substantial amount of time is managing to get a kernel on which I can ssh to
21:09.53Deubeuliousometimes it works, sometimes it doesn't
21:09.59mrmokuleviathan: hmm... I can't see anything in the recipe... probably something in the build system of the project?
21:10.12leviathanmrmoku: hmm
21:10.17leviathanperhaps
21:10.19leviathanits clisp
21:10.24DeubeuliouI have seen that the USB connector could switch between several modes, that could be interesting
21:10.27Deubeulioubye
21:10.59mrmokugot to go (to bed) too :)
21:11.02mrmokugnight all
21:11.15leviathanmrmoku|away: gn8
21:11.25leviathanmickeyl: do you have a snapdragon device?
21:11.47leviathanmickeyl: http://htc-linux.org/wiki/index.php?title=Tg01
21:11.52leviathanlooks very nice ^_^
21:12.21*** join/#openmoko-cdevel raster (~raster@enlightenment/developer/raster)
21:14.12*** join/#openmoko-cdevel naeg (~naeg@194.208.239.170)
21:18.00GNUtoo|laptopbye
21:22.10mickeylleviathan: no i don't have one. sounds all appealing, but given the nightmares we have with other devices, it won't become interesting for me until 100% of the peripherals work w/ standard linux interfaces...
21:23.38leviathanmickeyl: hmm, we have already rudimentary support in upstream
21:23.54leviathanI guess with 2.6.36 we will have official kernel working on dream
21:24.13leviathanwhich means, that we can get away from hackish leviathan-incoming
21:24.23leviathanand also use default kernel for dream
21:24.47leviathanI will also introduce alsa, as soon as we got the rest running properly
21:25.11mickeylinteresting. I'll be pleasently surprised when that comes. GPS, Bluetooth, and the sensors will take some more time i'm afraid
21:28.06leviathanyes, I fear, that will take much longer
21:28.45leviathangood thing
21:28.52leviathanits leaded by codeaurora people
21:29.01leviathanthey have the datasheets available
21:29.12leviathanbecause they have signed a NDA
21:29.42leviathanso, perhaps it won't take THAT long
21:29.45leviathanbut still long
21:29.45leviathan-.-
21:38.19*** join/#openmoko-cdevel DocScrutinizer (~halley@openmoko/engineers/joerg)
21:49.03*** join/#openmoko-cdevel mickeyl (~mickey@80.81.242.146)
21:57.41*** join/#openmoko-cdevel vanous123 (~vanous@194.228.223.3)
22:07.20zubevening
22:07.23zubwhere is JaMa?
22:58.34*** join/#openmoko-cdevel monocult (~monocult@dslb-088-077-181-028.pools.arcor-ip.net)
22:58.41*** part/#openmoko-cdevel monocult (~monocult@dslb-088-077-181-028.pools.arcor-ip.net)
23:53.37*** join/#openmoko-cdevel zidel_ (~zidel@cm-84.209.0.110.getinternet.no)
23:58.52*** join/#openmoko-cdevel ruoso (~ruoso@201009085231.user.veloxzone.com.br)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.