#qi-hardware IRC log for Tuesday, 2011-06-21

qi-bot[commit] Werner Almesberger: atusb/fw/usb/: added support for bulk IN EP 1 http://qi-hw.com/p/ben-wpan/244e44900:31
qi-bot[commit] Werner Almesberger: atusb/fw/: added reporting of RF interrupts via bulk EP1 http://qi-hw.com/p/ben-wpan/0120f6200:31
qi-bot[commit] Werner Almesberger: libatrf: new function atrf_interrupt_wait for interrupt-driven wait for interrupt http://qi-hw.com/p/ben-wpan/e6f0a1d00:31
qi-bot[commit] Werner Almesberger: tools/lib/: added interrupt_wait support to atusb and atusb-spi driver http://qi-hw.com/p/ben-wpan/110ecf600:31
qi-bot[commit] Werner Almesberger: libatrf: new function to reliably flush interrupts http://qi-hw.com/p/ben-wpan/620709a00:31
qi-bot[commit] Werner Almesberger: tools/: updated tools to use flush_interrupts http://qi-hw.com/p/ben-wpan/b0dd5ce00:31
qi-bot[commit] Werner Almesberger: tools/: added interrupt_wait support to atnet and atrf-proxy (untested) http://qi-hw.com/p/ben-wpan/668d8c600:31
qi-bot[commit] Werner Almesberger: tools/atrf-xmit/atrf-xmit.c: corrected title comment http://qi-hw.com/p/ben-wpan/106ef7f00:31
qi-bot[commit] Werner Almesberger: tools/lib/timeout.h, tools/lib/timeout.c: added timeout/deadline functions http://qi-hw.com/p/ben-wpan/4d4cec600:31
qi-bot[commit] Werner Almesberger: tools/lib/atben.c: added support for interrupt_wait (polled) http://qi-hw.com/p/ben-wpan/55354c700:31
qi-bot[commit] Werner Almesberger: tools/: major overhaul of wait_for_interrupt; uses atrf_interrupt_wait now http://qi-hw.com/p/ben-wpan/b4a6e8e00:31
qi-bot[commit] Werner Almesberger: atrf-xmit/atrf-xmit.c: updated to no longer use atrf_interrupt http://qi-hw.com/p/ben-wpan/b7276d200:31
qi-bot[commit] Werner Almesberger: tools/lib/atben.c (atben_interrupt_wait): complain about stray interrupts http://qi-hw.com/p/ben-wpan/9952a2000:31
qi-bot[commit] Werner Almesberger: tools/lib/misctxrx.c (flush_interrupts): don't fall back to reading IRQ_STATUS http://qi-hw.com/p/ben-wpan/76707d600:31
qi-bot[commit] Werner Almesberger: atusb/fw/: disable INT0 if manipulating GPIOs (tentative) http://qi-hw.com/p/ben-wpan/12fef1b00:31
qi-bot[commit] Werner Almesberger: tools/: the great removal of atrf_interrupt http://qi-hw.com/p/ben-wpan/d0fb1a800:31
qi-bot[commit] Werner Almesberger: libatrf: simplify use of atrf_interrupt_wait now this it is mandatory http://qi-hw.com/p/ben-wpan/10b6d8800:31
DocScrutinizer~cough~ messybox01:30
DocScrutinizerif infobot/apt was here, I'd ask her to tell about messybox01:32
rjeffriesok then http://thisismynext.com/2011/06/20/nokia-n9-lankku-leaks-images-renders/02:10
qi-bot[commit] Werner Almesberger: tools/lib/atben.c (atben_interrupt_wait): don't time out if timeout_ms == 0 http://qi-hw.com/p/ben-wpan/70715a102:16
qi-bot[commit] Werner Almesberger: tools/atrf-proxy/: make WAIT 0 wait forever http://qi-hw.com/p/ben-wpan/f4ca3ae02:16
qi-bot[commit] Werner Almesberger: prod/atusb (led): show keys to press in reverse http://qi-hw.com/p/ben-wpan/b2c772702:16
qi-bot[commit] Werner Almesberger: tools/lib/misctxrx.c (wait_for_interrupt): don't fragment timeouts http://qi-hw.com/p/ben-wpan/cb20c5502:16
qi-bot[commit] Werner Almesberger: tools/lib/atusb-common.c (atusb_interrupt_wait): don't try to pull more irqs http://qi-hw.com/p/ben-wpan/f8f2f8902:16
qi-bot[commit] Werner Almesberger: atusb/fw/: new request ATUSB_GPIO_CLEANUP to re-enable INT0 http://qi-hw.com/p/ben-wpan/f7b9a1802:16
qi-bot[commit] Werner Almesberger: tools/atrf-gpio/atusb.c (restore_gpios): send ATUSB_GPIO_CLEANUP http://qi-hw.com/p/ben-wpan/b0b04ed02:16
wpwrakrejon: we should announce our FISL talks on the qi-hw list. do you think the hours are reasonably dependable now ?02:30
rejoni haven't seen mine02:30
rejonno idea02:30
rejonagree on announce02:30
wpwrakrejon: you have two talks, Sat Jul 02 13:00 Qi-Hw. Sat Jul 02 17:00 Open Clip Art02:31
rejoni have one more on the 30th i just found out too, but that is another story, about acawiki.org02:32
rejonok, sure, sounds like they are set02:32
wpwrakrejon: a bit of an evil schedule02:32
wpwrakrejon: wow, 3 talks ! you'll be hoarse ;-)02:32
rejonyeah, its a bit out of hand02:33
rejonits ok, rather be busy than not02:33
xiangfukyak: Hi 02:37
xiangfukyak: I committed the 'backfire' branch on both openwrt-package and openwrt-xburst02:37
xiangfukyak: I think this time we using another method to rename the 'trunk' to 'master'02:40
xiangfukyak: maybe git push origin trunk:master, then we don't need modify the server config file, (I remember last time we rename the branch by 'git br -m' cause some more works)02:41
rozzincat urls.audio03:01
rozzinn/m :)03:02
DocScrutinizeranyway the often quoted mantra of N900 "It's NOT a phone, it's a computer" seems to shift to "it's not a computer" for N904:37
DocScrutinizeroops ECHAN04:38
rjeffrieswhatever they say in marketing-ese the device looks good04:38
rohthats basically a xmega based atusb04:39
rjeffriesat86rf230 ? I think..?04:41
wolfspraulroh: any news on cases or logo?04:43
rohrjeffries: afaik thats the predecessor of the one on the atusb/ben04:43
rohwpwrak: nope04:43
roheh wolfspraul 04:44
wolfsprauldo you have a timeline?04:44
wolfspraulall parts are there, right?04:44
rohwolfspraul: all beside the acryllic.04:44
wolfspraulI'm working on the last pieces on my end :-) box, labels, remote control seems almost settled too04:44
rohwolfspraul: pushin the final order there today04:45
wolfspraulah yes, please04:45
wolfspraultiming is still good, but it's getting tighter slowly :-)04:45
rohmy biggest concern is the gluing. the mill iss still not working and i need metal holders to align the small discs properly04:46
wolfspraulmill not setup/working in the new place yet?04:47
rohack. same with the laser.04:48
wolfspraulok, got it04:49
rohits getting a new cooling setup... i completed the exhaust last week04:49
qi-botThe build was successfull, see images here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.trunk-full_system-06202011-0123/04:49
wolfspraulok, well I wish you good luck, we need those cases soon...04:49
wpwrakroh, rjeffries: (at86rf230) a crappy predecessor. good luck with all its race conditions ;-)04:49
rohits loads of details moving so many machines needing a lot of 'support framework' to operate afzer all04:49
wolfspraulI can imagine. talk is cheap, I know how much work you have there to really deliver a full case...04:50
wolfspraulI'll ping you again towards the end of the week or so04:50
wolfspraulas long as box, labels and other stuff are still moving you are not the last one :-)04:50
rohwell.. i wish i could just focus on one thing every day.. but currently its a wild mix of everything to keep stuff going. quite annoying and tiring04:52
wolfspraulroh: btw, have you updated your m1 recently? it's getting quite nice to use now :-)04:52
rohbut i guess as long as you dont buy over a hundred cases a month from me that will not happen soon ;)04:53
rohwolfspraul: nope.. no time yet.04:53
wolfspraulone by one. But I do need those 80 soonish...04:53
wolfspraulI will keep you posted, as discussed.04:53
wolfspraulon one hand there is no need to stress out while other parts are in the making, on the other hand I want to avoid that the entire project is stuck at the end because we wait for cases.04:54
wolfspraulso I balance between those two...04:54
wpwrakroh: btw, if you want to go the 230 route, there's the ATMEGA128RZ series. avr, not avr32. built-in rf230. all going EOL, of course.04:54
rohwpwrak: ah. nope.. i didnt want to go anywhere. just noticed it in that shop04:55
rohwpwrak: btw.. atxmega vs atmega.. big diffence.04:56
wpwrakroh: ah :) yeah. nice. but already obsolete :) i'm quite glad we could switch to the 231. i had some qualms about the 230.04:56
rohatxmega is that thing between avr32 and avr. like a 'big brother' to the avr.04:56
wpwrakroh: don't know the xmega. fresher patents, i suppose ? ;)04:56
rohwpwrak: but good to know that the 230 and the 231 are that different04:57
rohwpwrak: its quite nice. has some really cool added features.. cleaned up the io pinning a bit.. faster, bigger. still really cheap.04:57
wpwrakroh: 230 has some bugs. like incoming packets overwriting old not yet retrieved packets. so you have to be very very quick. the 231 can avoid that.04:57
rohstuff like msample adc/dac and some irq framework which makes it nice for 'realtime' stuff04:57
wpwrakroh: then the 231 has the higher data rates. and they cleaned up some more things. ah yes, if you care about external RF PA or antenna diversity, then it's also the 231 and not the 23004:58
wpwrakroh: (xmega) hmm. so they dropped the fossils of avr. that would be a good move indeed ;-)05:00
rohits very similar. but different05:01
wolfspraulrejon: I find it so amazing how the networks in the US are racking up prices on wireless data now05:02
wolfspraulall but one have now removed the (never really) 'unlimited' data plans05:03
wolfsprauland the new plans are _expensive_05:03
rjeffriesfrom am arduino board re xmega: "Event System" that enables the peripherals, in conjunction with the DMA controllers, to do a lot of "common" things without having to involve the CPU at all.  Aside from allowing higher performance if the CPU is awake, this also allows the CPU to spend more time in assorted SLEEP modes, consuming less power.05:03
wolfspraulsomeone wants to reap the rewards of their investment dollars05:03
wolfspraula 2GB plan 30 USD / month, a 10 GB plan 80 USD / month (just reading about Verizon)05:04
rjeffrieswo;s[taul what doe you pay in China for a data plan?05:04
rejonyeah, not sure wolfspraul 05:06
rejonseems like they are getting cheaper to me05:06
wolfspraulwhich prices do you see?05:06
wolfspraulI was just comparing with atben, so atben can transmit 30KiB/sec, that means a little less than 10 hours for 1 GB05:07
wolfspraulif 1 GB at Verizon costs 8 USD now, that means atben can save you 20 USD a day :-)05:07
wpwrakwolfspraul: now we just have to bridge those few extra kilometers ;-)05:09
rohuhm. there are avrs with fpga cells?05:44
rohwell hidden on the page. wouldnt have found it without wikipedia and google05:44
kyakxiangfu: ping05:44
kyakxiangfu: before i did anything wrong, how should we do it this time?05:45
rohah.. but it seems eol-ed somehow.. also 6 years old http://www.design-reuse.com/news/10280/atmel-fpslic-ii-dynamically-reconfigurable-soc-supports-silicon-sharing-peripherals-interfaces.html05:53
xiangfukyak: hi06:02
xiangfukyak: I think I will run 'git push origin trunk:master' then 'git push origin :trunk' 06:02
xiangfuit's like overwrite, not rename(the last time we switch branch, we using git branch -m, which cause a little issue)06:03
xiangfukyak: if you think it's ok, I will run that now :)06:03
xiangfuthen for other people, git pull is enough.06:07
kyakjust one question06:08
kyakyou will overwrite the master branch with trunk contents06:09
kyakdoes it mean we will loose history of master?06:09
kyakalso, 'git push origin :trunk' means you would like to keep the trunk?06:10
kyakwhat for?06:11
xiangfu(for fun: https://github.com/MrMEEE/bumblebee/commit/a047be85247755cdbe0acce6)06:11
kyakheh yeah06:11
xiangfukyak: delete the remote trunk branch06:11
xiangfukyak: (lost master) no, I already commit a branch name 'backfire'06:11
kyakah, so you already saved the state of 'master'06:12
kyaki think it' sgood then :)06:12
kyaki also hope the history of 'trunk' in openwrt-packages will get restored somehow06:13
kyakcurrently it is lost for newly commited files06:13
kyakyou mentioned it is due to caching06:13
kyakbut not anymore it is not :)06:14
kyakmaybe this git web thing is not good at tracking other branches than 'master'06:14
xiangfukyak: shoudl not. the 'master' should same as other only different is the name.06:17
xiangfuthere is a merge come from dvdk.06:17
xiangfuyou mean openwrt-xburst right?06:18
kyakall newly added/modified files don't have history in web ui06:19
kyakno age, no message06:19
kyaknewly added -> i mean, in comparison to 'master'06:19
xiangfukyak: that a little bit strange. no age, no message06:26
xiangfukyak: I will do the rename on openwrt-package now. let see what happen06:27
qi-bot[commit] David Kühling: alex4: use left shift as fire key (left control missing on Nanonote) http://qi-hw.com/p/openwrt-packages/af0b29d06:27
qi-bot[commit] Xiangfu Liu: gtkguitune, swap left and right interface patch http://qi-hw.com/p/openwrt-packages/221303d06:27
qi-bot[commit] Xiangfu Liu: nanonote-files: reflash_ben.sh using -O in wget http://qi-hw.com/p/openwrt-packages/3ecb2ca06:27
qi-bot[commit] David Kühling: alex4: move save-files to ~/.alex4.* http://qi-hw.com/p/openwrt-packages/7d8785d06:27
qi-bot[commit] David Kühling: octave: fix fortran compile flags, enable parallel compilation http://qi-hw.com/p/openwrt-packages/c33acf006:27
qi-bot[commit] David Kühling: plplot: make compile again with openwrt trunk; switch to using cmake.mk http://qi-hw.com/p/openwrt-packages/01b5b1506:27
qi-bot[commit] David Kühling: new package: ASE: allegro sprite editor, a generic drawing and animation program http://qi-hw.com/p/openwrt-packages/682984006:27
qi-bot[commit] David Kühling: ase: hack gui to emulate mouse via keyboard; change keymap to not interfere. http://qi-hw.com/p/openwrt-packages/5c9e2b806:27
qi-bot[commit] David Kühling: ase: improved keyboard-mouse support: filter out arrow keys unless shift pressed http://qi-hw.com/p/openwrt-packages/33f9a7306:27
qi-bot[commit] David Kühling: liballegro: fix keyboard driver issues with nanonote's Fn key http://qi-hw.com/p/openwrt-packages/47a2f3f06:27
qi-bot[commit] David Kühling: liballegro: yet another keyboard fix for 'Fn' key. http://qi-hw.com/p/openwrt-packages/0244a5306:27
qi-bot[commit] David Kühling: ase: fix handling detection of number keys for zoom, ignore 'Fn' (LCONTROL) http://qi-hw.com/p/openwrt-packages/33eec1c06:27
qi-bot[commit] David Kühling: liballegro: make the fbcon fixes really water-tight (fix really all cases). http://qi-hw.com/p/openwrt-packages/a82661f06:27
qi-bot[commit] David Kühling: config.full_system (on trunk): add liballegro, alex4 and ASE (aseprite) http://qi-hw.com/p/openwrt-packages/f0b4b1906:27
qi-bot[commit] David Kühling: config.full_system (on trunk): enable libdumb, needed by alex4 http://qi-hw.com/p/openwrt-packages/a84f7d306:27
qi-bot[commit] kyak: Store/restore alsa settings correctly. http://qi-hw.com/p/openwrt-packages/ec8d8f806:27
qi-bot[commit] kyak: dega: add md5sum for tarball http://qi-hw.com/p/openwrt-packages/d8162a706:27
qi-bot[commit] David Kühling: liballegro: change the keybord driver fix to tread RCONTROL as before (as CTRL) http://qi-hw.com/p/openwrt-packages/026792a06:27
qi-bot[commit] David Kühling: ase: another keymouse fix: keep F1-F3 mouse-buttons from causing key events. http://qi-hw.com/p/openwrt-packages/cd0c7ce06:27
qi-bot[commit] kyak: vitetris: terminal-based Tetris clone http://qi-hw.com/p/openwrt-packages/c8ada0d06:27
kyakso, i'll try to git pull now06:28
rohhm. can we just disable that feat of the bot? its 'not helping' having it flooding the channel06:28
kyakno, it's totally helpful06:28
kyakit only floods sometimes06:28
kyakduring rebase06:28
rohnot when its flooding lots of commits in that style. is really hard to read so everybody will use a browser of git client anyhow. one line with a link to that would be enough.06:29
rohinstead of 2 screens full06:29
kyakxiangfu: i will now 'git co master; git pull', right?06:29
kyakroh: it's usually just one line06:29
xiangfukyak: wait06:31
wolfspraulroh: we limit it to 20 lines now, we can limit it further to 10 or so06:34
xiangfukyak: it should works fine. but I advice, 'git co -b temp; git br -D master; git co -b master origin/master'06:34
wolfspraulbut it gives an impression of a git merge so I don't think it's completely useless06:34
wolfspraulback when we had 500 lines it was not so much fun :-)06:34
rohhrhr.. the bot wasnt kicked due to flooding?06:35
xiangfukyak: make sure the 'master' is right. then you can remove the 'temp' and 'trunk'06:35
wolfspraulnah, the bot slows down06:35
wolfspraulit's a bot, it knows how to play the game...06:35
xiangfukyak: 'git co master; git pull' will cause small problems, since there are some file leave by 'trunk' and not delete in you local disk, remove those files should works fine.06:37
kyakxiangfu: following your advice, something is not right...06:38
kyaki was in trunk branch, i saved it with 'git co -b temp'. Then deleted master 'git br -D master'. Then stashed my changed 'git stash'. Then checkout remote master 'git co -b master origin/master'06:39
kyaknow i try to restore my stashed changed06:39
kyakby theere is a conflict06:39
kyakbut there shouldn't be any conflict06:39
kyakbecause i went there right from trunk, which is master now06:40
xiangfukyak: have you run 'git fetch -a' first? 06:41
xiangfuupdate your local origin/*06:41
kyakthat's a good idea :)06:41
xiangfuit's needs run 'git fetch -a' first sorry06:41
kyakyep, i udnerstand now06:41
xiangfuor you master still the old :)06:41
xiangfuif it's works fine in your side, let's do this on openwrt-xburst, then send email to list. 06:42
kyakok, everything went fine06:47
kyaki will now remove local trunk and temp06:48
kyakxiangfu: will you remove remotes/origin/trunk as well?06:49
xiangfukyak: in the server side, it's already removed, in locally, we need run 'git remote prune  origin'06:51
kyakcool :)06:52
xiangfukyak: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.trunk-full_system-06202011-0123/failed_packages.txt cool, thanks, not much package failed to build.06:55
kyakyeah, just several packages06:55
kyakand they are not too important06:56
qi-bot[commit] Xiangfu Liu: uboot-xburst: update to 2010.06 http://qi-hw.com/p/openwrt-xburst/bf95bd707:57
kyakxiangfu: the last commit? :)08:00
xiangfukyak: yes08:00
qi-bot[commit] Mirko Vogt: add <http://downloads.qi-hardware.com/software/mirror-openwrt-sources/> http://qi-hw.com/p/openwrt-xburst/a37eea908:01
qi-bot[commit] Xiangfu Liu: optimize for ben nanonote http://qi-hw.com/p/openwrt-xburst/0f4354508:01
qi-bot[commit] Xiangfu Liu: [xburst] Improve mounttime http://qi-hw.com/p/openwrt-xburst/c868d4608:01
qi-bot[commit] Xiangfu Liu: nanonote optimize http://qi-hw.com/p/openwrt-xburst/c1dba4c08:01
qi-bot[commit] Xiangfu Liu:  Add-gfortran-compiler-support-to-the-toolchain http://qi-hw.com/p/openwrt-xburst/cf4b09908:01
qi-bot[commit] kyak: add kernel patch for setfont2 http://qi-hw.com/p/openwrt-xburst/dd385c408:01
qi-bot[commit] Xiangfu Liu: optimize for ben nanonote http://qi-hw.com/p/openwrt-xburst/797be6b08:01
qi-bot[commit] kyak: config-2.6.37: enable battery, disable RNDIS http://qi-hw.com/p/openwrt-xburst/a3d8a8b08:01
qi-bot[commit] kyak: patches-2.6.37: support for Ben NAND partitioning http://qi-hw.com/p/openwrt-xburst/83f076a08:01
qi-bot[commit] David Kühling: linux kernel: add CONFIG_PROC_PAGE_MONITOR=y to allow for clean user-space DMA http://qi-hw.com/p/openwrt-xburst/fbaf65508:01
qi-bot[commit] kyak: config-2.6.37: enable options needed for keymouse http://qi-hw.com/p/openwrt-xburst/e74aa2b08:01
qi-bot[commit] kyak: trunk: fix kernel keymap for VolUp/Down and Del http://qi-hw.com/p/openwrt-xburst/b35d1cf08:01
qi-bot[commit] kyak: trunk: build sound modules in kernel http://qi-hw.com/p/openwrt-xburst/0942c3608:01
qi-bot[commit] kyak: trunk: add ks7010 support patch http://qi-hw.com/p/openwrt-xburst/5e6fcae08:01
qi-bot[commit] Xiangfu Liu: base-files, move it to openwrt-package/nanonote-files http://qi-hw.com/p/openwrt-xburst/cbc84e108:01
qi-bot[commit] kyak: uboot-xburst: don't install empty dir http://qi-hw.com/p/openwrt-xburst/bce1b8d08:01
qi-bot[commit] kyak: Disable syslogd and klogd http://qi-hw.com/p/openwrt-xburst/467647c08:01
qi-bot[commit] David Kühling: Merge branch 'trunk' of projects.qi-hardware.com:openwrt-xburst into trunk http://qi-hw.com/p/openwrt-xburst/3ab144408:01
qi-bot[commit] David Kühling: cmake.mk: fix bogus values for FIND_ROOT_PATH_MODE_*; kept plplot from compiling http://qi-hw.com/p/openwrt-xburst/e1cbfbf08:01
qi-bot[commit] Xiangfu Liu: uboot-xburst: update to 2010.06 http://qi-hw.com/p/openwrt-xburst/bf95bd708:01
kyakxiangfu: should be get rid of that merge by dvdk?08:03
xiangfukyak: when rebasing.08:03
kyaki'm trying to push dvdk's last fix for cmake upstream: https://dev.openwrt.org/ticket/957308:04
kyakperhaps we can rebase after it's accepted08:04
xiangfukyak: done on openwrt-xburst. please test again : http://dpaste.com/556876/08:06
kyakyep, doing it now08:06
kyakxiangfu: it went very well :)08:08
kyakxiangfu: now, the history in web ui is restored08:09
xiangfuI am sending the email, then update the script file, (maybe the old http://fidelio.qi-hardware.com/~xiangfu/bin/compile-openwrt-xburst.sh,  will works fine)08:10
kyakxiangfu: i'll just add one lien to compile-openwrt-xburst.sh (to create failed_packages.txt)08:13
xiangfukyak: you can compare the compile-openwrt-xburst-trunk.sh and compile-openwrt-xburst.sh  a little. then we just remove the compile-openwrt-xburst-trunk.sh.08:14
DocScrutinizer(<wolfspraul> it's a bot, it knows how to play the game...) LOL08:14
xiangfukyak: then update 'compile-openwrt.sh' 08:14
DocScrutinizermoinmoin everybody08:14
kyakxiangfu: btw, there is a git repo in ~/bin08:14
kyakxiangfu: ok, i think compile-openwrt-xburst.sh should be ready now08:19
kyakxiangfu: should i stop the current build and restart it with compile-openwrt-xburst.sh?08:21
xiangfuyes. let's do it08:23
xiangfuI think we should remote the entire openwrt-xburst.trunk-full_system, useless from now on.08:25
kyaki left the tree latest trunk-full_system, just for us to check if something goes wrong08:29
kyakoh, you mean the build directory itself08:30
kyaki suggest that we wait until the openwrt-xburst.full_system-06212011-1026 build is finished08:31
xiangfuI mean the ~/openwrt-xburst.trunk-full_system08:31
xiangfuthe build image is fine08:31
xiangfukyak: yes. that sounds better.08:31
wolfspraulDocScrutinizer: moin08:32
kyakxiangfu: i removed the link public_html/openwrt-xburst.trunk-full_system to avoid confusion.. Let's keep it locallly for some time :)08:33
kyakso now we wait :)08:38
DocScrutinizerunrelated: Nokia announced their new phone N909:41
DocScrutinizerno hw kbd, capacitive ts... pffff09:41
DocScrutinizerno uSD slot, double-plus-PFFFF09:41
DocScrutinizernow if at least it came with dual-sim09:42
DocScrutinizerno OTG, no hostmode - three extra loud PFFFF LOSER09:44
Jay7why they release it then? :)09:45
Jay7it have no difference with 1xxx series :)09:45
DocScrutinizerthey promised a "meego" devie for this year though09:46
DocScrutinizeroops not this one :-D09:46
DocScrutinizeractually the first link point to a better phone09:47
kyakthe worst thing is that the SW platform is more dead than alive09:56
DocScrutinizerindeed, 'meego'(maemo)-harmattan seems stillborn09:58
DocScrutinizerand it's but-ugly09:59
DocScrutinizerback-to-winCE design and concept09:59
DocScrutinizeranyway on popular demand I applied for a N950 N9-developer-device10:00
DocScrutinizerlet's see if that's at least a bit better, usability wise, as it got a hw kbd10:00
DocScrutinizer*allegedly* hw is identical, modulo the slide-out kbd10:02
DocScrutinizerwell, if my Nokia patrons speak up to get me one of the 250 devel devices...10:03
DocScrutinizerI really don't get it why they don't market N950 rather than or in addition to N910:04
DocScrutinizerallegedly CE cert problems, muhahaha10:04
DocScrutinizerif Nokia boggles to print that CE self-issued cert icon on their box, then for sure there's sth severely odd with the hw10:05
kyakDocScrutinizer: i read that N950 has some disadvantages to N910:07
DocScrutinizerhalf the ram at least10:08
kyakTFT LCD10:08
kyakworse battery10:08
DocScrutinizerif that 1GB ram of N9 isn't marketing speak again10:08
kyakno warranty10:08
DocScrutinizerooh, no amoled, naaawww10:08
kyakit doesn't matter for you, right? :)10:08
DocScrutinizerno warranty? lol, they lend me the thing10:08
kyakwhere is this article...10:09
DocScrutinizerthough it seems Nokia never reclaimed their lend-outs10:09
DocScrutinizertoo expensive10:09
DocScrutinizermight be different here, given the limited number of devices available10:10
kyaki heard about 25010:10
DocScrutinizerfor "community"10:10
kyakwhat are your chances receiving one of them?10:10
DocScrutinizerthink they got some more for contractors10:11
DocScrutinizerwell, konttori partonising me10:11
DocScrutinizerhe sugested I should apply and he'll talk to the guys managing the program10:11
DocScrutinizerhe seems aware I actually can help occasionally10:11
DocScrutinizerI asked him to fix the SSC problem on N900 (*#67#)10:12
DocScrutinizerand I published starhash-enabler to TADAAAA insert that one line into that config file10:12
kyaki totally didn't understand your last two phrases, but sounds cool :)10:13
kyakDocScrutinizer: if you wanted to buy a smartphone for yourself now, what would it be?10:14
DocScrutinizerconsidering to get a spare spare as long as there are some available10:15
DocScrutinizerespecially since Nokia can't even repair them now just 18 months after rollout - they swap for an N8 when you send in a N900 for warranty repair10:16
kyakare they not produced anymore?10:16
DocScrutinizerobviously not10:16
kyakheh, why would they do that to N900?10:16
kyaki heard from many geeks they love it10:17
DocScrutinizerand seems they even missed to keep a reasonable stock for replacements10:17
DocScrutinizerI guess, due to several problems with quality etc, Nokia decided to call it broken by design and to discontinue and rollback10:18
DocScrutinizerthey better came up with a N900-i and a improved more open maemo10:19
DocScrutinizerbut meh, you know, Elopocalypse10:19
kyakso they gave a toy to a child and then took it away10:20
kyakdespite of the fact that the child doesn't really care if the toy is broken or not :)10:20
DocScrutinizerthey gave a violin to a 4 year old, and when he grew out of it at age of 9 they refused to give a proper violin for grownups10:21
kyaki think my Nokia N73 is slowly dying and it's time i start thinking about replacement...10:21
DocScrutinizerrather refuse to even service the baby violin anymore10:21
kyakyeah, that's a kind of strange logic..10:22
DocScrutinizer""look, there's that nice synthesizer kbd from Redmond, go use that for playing music""10:22
kyakand Nokia surely lost some of their fanboys after coupling with MS10:23
DocScrutinizerquite some, yes10:23
kyakwhere did they go?10:23
kyaknot to Samsung, obvisouly10:24
DocScrutinizerlost even more though of the maemo community when they deliberately put them down the 3rd time10:24
DocScrutinizermost went to andridiot10:24
DocScrutinizersome still cling to "true meego"10:25
DocScrutinizeraka #meego-arm10:25
kyakinteresting.. like, running meego on HTC devices?10:25
DocScrutinizerit's all a giant fsckng deja-vu regarding what OM did10:25
DocScrutinizernah, I guess they'll try to bring true meego handset UX to N9 now10:26
DocScrutinizerthey are about (or did already) to rollout meego for N90010:27
DocScrutinizercalled meego 1.2 CE10:27
DocScrutinizerfor Community Edition10:27
kyak'CE' ffs10:27
kyaknot the best choice of abbreviation :)10:27
DocScrutinizerwellknown Carsten Munk of Mer a leading head of that enterprise10:27
DocScrutinizerit's been DE for developer edition formerly ;-P10:28
Action: DocScrutinizer is pondering to watch some threads on talk.maemo.org explode10:29
DocScrutinizerI bet you can't read as fast as they scroll10:29
DocScrutinizerthe announcement been like 6h ago10:30
kyakit's interesting how fast it happens. I had no clue about Nokia development of N9/N950 just yesterday10:30
DocScrutinizerit's been in the rumours for like 9 months now10:30
kyakmakes me wonder what would happens "tomorrow"10:30
kyakyeah, probably, i'm just not inside this subject10:31
DocScrutinizerexcept maybe Elop gets killed by dropping a stinking oistrich egg at him ;-P10:31
Action: DocScrutinizer wonders where to get the rotten ostrich egg from10:32
kyakyou should get yourself an alibi in case it happens for real tomorrow :)10:32
kyakremember - public logging!@10:32
DocScrutinizerI'll log tomorrow as well, ( <- checks alibi)10:33
kyakthey'd say you had used Eliza bot :)10:34
DocScrutinizerI *am* Eliza bot ;-)10:34
Jay7I'm happy to see that SonyEricsson and Samsung are opening devices slowly10:43
Jay7at least no crypted loaders10:43
Jay7ah, I understand10:45
Jay7DocScrutinizer: they will say now that Meego devices are unpopular and close this line10:45
kyakthanks to crackers, companies now decide that it is better to keep it open from the beginning than to embarass themselves when it is cracked anyway10:45
Jay7and price is about $1k10:46
Jay7kyak: http://habrahabr.ru/company/Nokia/blog/122265/10:47
Jay7russian release :)10:47
DocScrutinizerJay7: indeed the idea to roll out a meego device without hw kbd looks like another perfect step in a plan to kill off the whole "linux-on-a-phone" thing10:49
DocScrutinizeras somebody just mentioned at #maemo, you won't please hardcore maemo/meego-hackers with the N9, and it's highly unlikely users that never were interested in linux at all now will switch to that new "ecosystem" that has no apps, no competitor devices, nuttin10:50
kyakJay7: yeah, i've read it. Can't help admiring the stupidity of Nokia representative10:53
lekernelOpenmoko should just have looked like the iPhone10:55
lekernelso this would excuse price10:55
lekerneland make a very attractive device10:55
Jay7time for NanoNote phone editions10:55
lekerneltime to get rid of cruft like X11, pulseaudio etc.10:55
Jay7qt4 :)10:55
lekerneland make an outstanding GUI10:55
kyakasking the question like "What do you think would be the price for N9?" to the audience of students and then not being able to defend his grounds10:55
lekernelqt4 is still nowhere near the IOS GUI10:56
lekerneland it's very slow and bloated10:56
Jay7efl then :)10:56
lekernelenlightenment is on the right path, except that they have trouble getting things done10:56
Jay7well, toolkit is choosen :)10:56
Jay7people are talking about some developer device with HW keyboard..10:57
kyaklast time i heard from bartbes, enlightenment coudln't work without X10:57
kyakhe tried to make it work on Ben10:57
DocScrutinizerdiff N9 vs N950 hw: http://pastebin.com/0SWqx8JL10:57
lekernelefl should be able to work without tons of problems in the absence of X10:57
lekernelI even have already compiled bits of it for RTEMS/Milkymist10:58
Jay7I fear price of N950 then..10:58
lekernel"The EFL begins with Evas, our canvas library. Because Evas is built on several different selectable engines (Linux FrameBuffer, DirectFB, X11, OpenGL/OpenGL-ES, QTopia, etc) the platform is extremely portable, which translates thru to all of the libraries built on top of it."10:58
DocScrutinizerJay7: N950 won't go retail10:59
DocScrutinizerdeveloper device only10:59
kyakok, sounds promising.. Perhaps need to have a look10:59
Jay7then it will not work from battery10:59
Jay7I'm sure :)11:00
DocScrutinizereven an extremely rare one: only 250 available to community11:00
lekernelit should have some hw acceleration too... I don't know the status of it11:00
Action: Jay7 remembers qt greenphone11:00
Jay7Elopocalypse, as you said..11:00
lekernelthings like software scrolling are slow, even on modern embedded devices11:00
DocScrutinizeropenmoko's "predecessor"11:00
bartbeskyak: EFL works, e17 doesn't11:04
kyakbartbes: but what can you do with EFL, without e17?11:07
kyakalso, how would it correlate with their "the platform is extremely portable"?11:08
kyakare these just words, again?11:08
jivsi'm stuck on "kernel panic- not syncing: VFS Unable to mount root fs on unknown-block(0,0) " msg11:09
bartbeskyak: develop applications ;)11:09
bartbesEFL is like gtk11:09
jivshow can i put it to usbboot mode again.11:09
bartbesand e17 is gnome11:09
jivsi tried to reflash it with my own images.11:09
kyakbartbes: ok, good point. I don't expect gnome to run in DirectFB :)11:10
kyakjivs: try powering it on while holding the 'u' key11:11
kyakand watch for dmesg11:11
kyakthen you can use reflash_ben.sh to reflash11:11
jivstried so.. doesn't go to boot mode. when i connect to usb cable. it boots up and the same msg again11:12
kyakbartbes: are you aware of any efl-based applications that can run in DirectFB (i.e. on Ben)?11:12
jivsdmesg: i am not sure about it.11:12
kyakjivs: hold the 'u' while pluggin in the USB cable (i.e. while powering on)11:13
jivskyak, thank you11:24
jivslooks im in boot mode now. i will try to reflash it now.11:24
bartbeskyak: ehm, basically everything that's not the wm, supposedly :P11:34
bartbesanyway, edje is supposed to be a super-easy way to create applications11:35
bartbesscripted and all11:35
kyakbartbes: it's hard to believe that it is just e17 that doesn't work11:35
kyaki assume there are a lot of apps dependent on e1711:35
bartbeswell, as mentioned, efl's graphics thingy has a directfb backend11:36
bartbesso only things that need direct X access (the wm) or opengl won't work11:36
bartbesor well, that's supposedly the truth11:36
kyakokay then... maybe we can try finding something usefull for Ben11:37
kyakand fast? :)11:37
bartbeswell, as I said edje applications should work11:37
bartbesso perhaps if you manage to work out how that works you can write an SDL-less gmenu alternative11:38
bartbesit's been a while since I played with the EFL though11:39
dvdkxingfu: what's up?12:07
qi-bot[commit] Werner Almesberger: TODO: updated with current tasks http://qi-hw.com/p/ben-wpan/15db27912:25
xiangfudvdk: hi14:05
xiangfujust want let you know that we do the 'rename' on openwrt-xburst and openwrt-package14:07
xiangfudvdk: you maybe already saw the email14:08
dvdkhi xiangfu, already saw your mail and typed in those commands.  worked like a charm.  thx14:08
xiangfudvdk: great. also kyak have cleaned up a little on buildhost.14:08
jivshow can i submit a patch for openwrt Makefile, it is one of the package qi-hardware site14:39
jivsit's the libsdl-gfx package14:40
xiangfujivs: you can send the patch to mailing list. 14:41
xiangfujivs: or if you want working more on openwrt package. I can make you have write access, then you can direct commit it14:41
xiangfujivs: BTW: we update a little recenlty on openwrt-package.git which branch you are working on?14:42
xiangfujivs: please have a look at : http://lists.en.qi-hardware.com/pipermail/discussion/2011-June/008326.html14:42
jivsit's trunk14:43
jivsso i believe must be latest14:43
jivsshall i check the revision14:43
xiangfujivs: ok. then it should apply fine on our new 'master' which is the 'trunk' before rename.14:43
xiangfujivs: we just do the rename. so you can just backup your commit first. then follow the email commands, apply it again.14:44
xiangfujivs: do you have account on http://projects.qi-hardware.com/?14:44
jivsxiangfu, ok14:44
xiangfu(patch) then you can send to mailing list/me or give you write access on openwrt-package.git if you want.14:45
jivsi will email the patch to the mailing list today14:45
xiangfujivs: ok. thanks for patch :)14:45
jivsxiangfu, i do not have yet14:45
jivsxiangfu, welcome14:46
jivsit's just update the Makefile so that it copies the  .pc file to the pkgconfig folder..14:46
xiangfuI like small patches :)14:47
xiangfueasy understand, easy apply and it do fix something :D14:49
jivsi have sent email on the mailing list, plz apply it when you receive14:52
jivsxiangfu, Till now i was getting the openwrt toolchain from the Openwrt website itself and selecting the Ingenic xburst to build my toolchain14:53
jivsas i found the qi-hardware wiki bit complex to follow14:54
jivsbut the images i get from the openwrt ingenic toolchain doesn;t seem to work.14:55
rejonwpwrak, http://softwarelivre.org/fisl12/speakers20:33
wpwrakrejon: yeah ! progress ! ;-)20:37
wpwrakrejon: and you even got the pole position ! richly deserved with all the talks you'll give :)20:37
kristianpaulbtw i cant get the schedulle to load, just lot of non-formated text afaik... :?20:38
wpwrakkristianpaul: it fails for me with konqueror but works with firefox 3.6.1620:39
dvdkwpwrak: about your busybox sh bug:20:41
dvdkwpwrak: look at these bash bugs I stumbled upon when coding my last project in shell script :20:41
wpwrakdvdk: bah, all fancy stuff. that's what you deserve for using bashisms ;-) 20:43
dvdkbut without bashisms, sh is hardly turing complete :)20:44
wpwrakdvdk: perhaps the correct approach would the be to implement a turing machine in /bin/sh, then program that one. this should eliminate your worries, no ? :)20:57
dvdkwpwrak: you're not the first propose that :) http://www.forthfreak.net/index.cgi?BashForth20:58
dvdkalthough this one needs bash not sh20:58
wpwraknice ;-)21:01
Action: kristianpaul consider one more time use lua as scripting language21:02
Action: dvdk is a tcl fan21:03
dvdknever try to use bash's arrays for more than a few elements.  insertion quickly becomes O(N)21:03
kristianpaulhum, how i can avoid tha bashisms, acording to wikipedia that cut portability with other Bourne shell implementations21:12
kristianpauloh, well21:13
Action: whitequark clearly remembers that someone has sent him UBBs, but who may be that?..21:14
whitequarkdvdk maybe?21:14
dvdkany news about them?21:15
whitequarka notification has not arrived21:34
whitequarki may go to the postal and ask them, but I need the tracking number then21:35
whitequarkalso, bitcoin has crashed recently. still want me to pay with it? :)21:35
whitequark*B$ market21:35
dvdkwhitequark: let's wait with discussing payment, until it actually arrives.  i think we should just continue waiting.  21:59
dvdkjust checking tracking number21:59
dvdkstatus is still "passed in frankfurt/de for transmission to russia"22:01
--- Wed Jun 22 201100:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!