#qi-hardware IRC log for Wednesday, 2010-12-01

wolfspraulwpwrak_: ok I cleaned it up a bit... http://en.qi-hardware.com/wiki/Community_news_2010-12-0100:11
wolfspraulxiangfu: there is an error report for fped at Debian, see http://qa.debian.org/developer.php?login=xiangfu%40sharism.cc00:14
xiangfuwolfspraul: don't understand the error. will ask debian people. in #debian-mentor00:19
xiangfuform the #debian-mentor:00:23
xiangfu<pabs> since upstream doesn't do releases, just ignore it00:23
xiangfu<pabs> or poke upstream to have proper software development practices00:23
wolfspraulI'm sure Werner will love that...00:28
qi-bot[commit] Xiangfu Liu: update the homepage to help webpage http://qi-hw.com/p/fped/5a5bc8c00:28
rohbut if you put the wan if into the right zone it should just work00:41
kyakxiangfu: hey! i've made a small patch for reflash_ben.sh to show a progress bar - http://downloads.qi-hardware.com/people/kyak/tmp/reflash_ben.progress.patch01:57
kyakxiangfu: would be great if you could test01:57
xiangfukyak: thanks. I will test it.01:57
xiangfukyak: great. works pretty good.02:27
kyakgood. i'll commit then?02:29
xiangfukyak: yes.02:31
qi-bot[commit] kyak: reflash_ben.sh: add progress bar http://qi-hw.com/p/openwrt-xburst/5cb808802:33
kyaki thougth the next step could be to output the spent time/ left time, but i noticed that the transfer is somwhat not continous02:34
kyaki.e. it transfer 16 times, then it waits for somethinfg02:34
kyakso maybe better leave it like it is.. at least now we have an impression how much is left to reflash02:35
xiangfukyak: yes. sure.02:35
kyakxiangfu: do you know why it works like this? i.e. transferring 16 times, then waits02:36
xiangfukyak: i am not sure.  it's PIPO issue.02:39
xiangfu(guess) only the PIPO is full or EOF, then "tee" will send message out.02:40
kyakPIPO,, have to google that02:40
xiangfusorry FIFO02:40
kyakno, it's not tee02:40
kyakit's really what happens02:41
kyakyou can start tail -f log.txt in once console and reflash_ben.sh (previous version) in another02:41
kyakyou'll see this thing02:41
kyakyou'll see that it really waits between these series of 16 blocks02:42
kyakor whatever it is02:42
kyaki never really noticed it before02:42
kyakbefore i watched this process with a progress bar02:43
xiangfuI know that. only when we use script file , the log.txt will like that.02:43
xiangfuso 'shell' must cache the output.02:44
xiangfuneed someone really understand the 'shell' can answer this question. I am not sure.02:45
kyakthen the script itself has a problem?02:45
kyaki'll try launching it without the script.. i.e. just the nprog 2048 ${WORKING_DIR}/${ROOTFS} 0 0 -n (from usbboot console)02:46
xiangfuthe script file it's like: "3>> "${LOG_FILE}" 2>&1 >&3"02:46
kyaki wonder what i'll see nprog 2048 ${WORKING_DIR}/${ROOTFS} 0 0 -n02:46
kyaki wonder what i'll see in this case02:46
kyakif it will be a continous output02:46
kyakwhich i doubt02:47
kyaki know how it was before in script file.. i spend pretty much time trying to figure out that "3>> "${LOG_FILE}" 2>&1 >&3" thing02:47
xiangfukyak, direct run "usbboot ...". the output will continue.02:47
kyakthen the script has a bug02:47
kyakit's ok that the script writes to the log file after some caching.. but things going to stdout must be instant02:51
xiangfukyak: there is some code "usleep(100);, sleep(1)" in usbboot.  is that the problem ??02:56
kyakxiangfu: i'm not sure.. i can't test the usbboot right now -\02:57
kyakbut the delay is more than 1 second02:57
kyaki suspect that usbboot might be delaying it's output02:58
kyakor waiting for something02:58
kyakbut it is needed to be tested outside th escript02:58
xiangfuwhen direct run "usbboot". the output just fine. no delay at all. ( I always direct run "usbboot")03:00
kyakoh ok..03:00
kyakit's hard to judge though, because the lines are the same all the time03:01
kyakat some point it may appear that the screen is not changing at all03:01
kyakin my test script, there is no delay03:04
kyakthat's why my assumption is that it is coming from usbboot03:04
kyakbasically the test script is the same, only there is another script that simualtes usbboot output03:06
xiangfucan you send the test script files to me.03:06
kyakone sec03:06
kyakthe reflash.sh simualtes usboot output03:08
kyakyou run progress.sh03:08
kyakif there is not delay in reflash.sh output, there is no delay in progress.sh indication03:08
kyakyou can customize the delay and number of blocks to "write" in reflash.sh03:10
xiangfukyak: strange. don't know why. :(03:17
kyakxiangfu: btw, the usbboot - is it written by qi, or is it from ingenic?03:19
xiangfukyak: by Qi: http://projects.qi-hardware.com/index.php/p/xburst-tools/source/tree/master/03:20
kyakoh, great.. at least we have a full control over all of those things03:21
kyak(i still rememeber triggerhappy) :)03:21
wpwrak_xiangfu, wolfspraul: (fped error) so .. no action required ? :)04:09
wpwrak_wolfspraul: (wpan antenna) btw, here's a picture of my antenna farm: http://downloads.qi-hardware.com/people/werner/tmp/antfarm.jpg04:11
wpwrak_original: http://downloads.qi-hardware.com/people/werner/tmp/IMG_0661.JPG04:11
wpwrak_wolfspraul, kristianpaul: (community news) the 150 MHz scope - is it the only one the university has ? if not or uncertain, maybe write "to a 150 MHz scope"04:14
wpwrak_wolfspraul: (mm1) how about mentioning that the case parts were laser-cut ?04:14
wpwrak_wolfspraul: (xue) maybe add more emphasis on xue looking for reviewers ? right now, it sounds a bit like something that'll happen anyway, without any reader needing to get involved. e.g., something like "Andr\'es Calder\'on has issued a call for reviewers."04:18
wolfspraulha :-)04:20
wpwrak_wolfspraul: in fact, maybe put the CMOS sensor and the call for review as two items. the CMOS sensor also has the "choice" element, right ? or has this been covered before ? So "The Xue project has chosen the .... . In a leap of faith, ... a firm order of 30 sensors."04:20
wpwrak_hmm, too bad that jlime didn't make it into this news batch04:23
wolfsprauldon't know what exactly the news is there, someone just needs to write it up04:24
wpwrak_(jlime) i think it's "almost done", but with a few loose ends. not sure about rafa's schedule (or anyone else's for that matter)04:28
wpwrak_ah ... maybe "upcoming events": the MM1 workshop at CCC !04:31
wpwrak_now. the moment of truth. yesterday, after the thunderstorm, my antenna tests all of a sudden started to change. could be something in the test setup or could be just bad luck with all the antennas i tested at the end (three of them) having the same flaw causing an unusual profile.05:13
wpwrak_the tree that drop to ~ -31.5 dB around 2440 MHz. that's not a normal curve.05:16
wpwrak_oops. make that http://downloads.qi-hardware.com/people/werner/wpan/tmp/ants-s2-weird-change.png05:19
wpwrak_grmbl. one the antennas that tested okay before now also acts weird :-(05:21
qi-bot[commit] Xiangfu Liu: move ks7010 firmware to it's package http://qi-hw.com/p/openwrt-xburst/0403a6a05:26
qi-bot[commit] Xiangfu Liu: move those example file to a new package: nanonote-example-files http://qi-hw.com/p/openwrt-xburst/4e3b2db05:51
qi-bot[commit] Xiangfu Liu: new package, nanonote example files package http://qi-hw.com/p/openwrt-packages/ca85c0706:00
wpwrak_intersting ... power-cycle all devices, reconnect antenna. voila, signal is some 15 dB stronger than before. WFT ?!? :-(06:12
wpwrak_it does look a lot "cleaner", though. i wonder what happened before.06:13
qi-bot[commit] Mirko Vogt: disable fbterm and lynx, since they do not compile... latter one should be easy to fix (missing iconv.h) http://qi-hw.com/p/openwrt-xburst/d170cb706:38
kristianpaulwpwrak_: (scope) no, i also used some multimeters, PSU06:43
kristianpaulwpwrak_: they also had an spectrumanalizer but i dint used at last06:44
kyakmirko: they DO compile06:45
kyakthey require locale to be enabled06:45
kyaktherefore patch for fbterm was removed06:45
kyakyou might be missing one of the commits to openwrt-xburst06:46
kyak1b577b72608d4cd16de089a5d8eee419cf9ab4b2 this one, to be specific06:47
kristianpaulwpwrak_: (ants) weird changed indeed, your finding could be interesting for nokia ;)06:47
mirkokyak: hmm, did i miss to update the qi-packages repo first? (thinking...)06:48
kristianpaulactually it looks like more the oposite signal06:48
kristianpaul"oposite" or english equivalent06:49
kyakmirko: well, if both openwrt-packages and openwrt-xburst are updated to the latest master, they compile06:49
mirkoit is06:50
mirkoupdated and started the full build yesterday06:50
mirkoupdated both repos to latest HEAD, re-enabled them and will test again06:53
kyakand your feeds.conf are using the latest version of qi-packages?06:54
kyakok then.. pretty strange though because xiangfu also didn't complain06:55
kyakmirko: are you building from scratch?06:56
wpwrak_kristianpaul: (nokia) hmm, i think they know RF a lot better than in could every hope to ;-)06:57
kristianpaulwpwrak_: sure just kidding06:58
qi-bot[commit] carlos: Adding PS2, capacitive keyboard examples http://qi-hw.com/p/nn-usb-fpga/62d0edf08:40
qi-bot[commit] Werner Almesberger: atusb: use 0402 as the preferred component size and replace bad TVS http://qi-hw.com/p/ben-wpan/23c372609:10
qi-bot[commit] Werner Almesberger: usrp/README: change threshold to avoid making section reference look like a typo http://qi-hw.com/p/ben-wpan/fea4ee509:10
qi-bot[commit] Werner Almesberger: usrp: try to bring back sanity to pre- and post-processing of FFT data http://qi-hw.com/p/ben-wpan/40d123409:10
qi-bot[commit] Werner Almesberger: ants/cam: update for latest workpiece http://qi-hw.com/p/ben-wpan/04972bb09:10
qi-bot[commit] Werner Almesberger: usrp: update filtering and display for uncorrupted measurement setup http://qi-hw.com/p/ben-wpan/b3c0b4b09:10
qi-bot[commit] Werner Almesberger: usrp/doall: usage and allow passing of arguments to evscan as well http://qi-hw.com/p/ben-wpan/e52b92f09:10
qi-bot[commit] Werner Almesberger: usrp/range: more useful diagnostic output and harden against underflows http://qi-hw.com/p/ben-wpan/8ea171509:10
qi-bot[commit] Werner Almesberger: atusb: updated footprint assignment http://qi-hw.com/p/ben-wpan/9ad060909:10
qi-bot[commit] Werner Almesberger: atusb/cam: modernize, and change setup for current workpiece http://qi-hw.com/p/ben-wpan/e137bc409:10
qi-bot[commit] Werner Almesberger: atusb: remove two unnecessary test points http://qi-hw.com/p/ben-wpan/521dab811:33
wpwrak_wolfspraul: you did it ! congratulations !!11:37
wolfspraulthe news? yeah11:39
wolfspraulI could have mentioned the Milkymist One RC2 production, forgot... but also no tangible enough results yet11:39
wpwrak_(mm1) you could have mentioned the upcoming workshop11:43
wpwrak_(i wrote this before. not sure if you saw it.)11:44
wolfspraulI don't like 'upcoming' stuff11:55
wolfspraulso I don't add it :-) it's a wiki...11:55
wolfspraula few times I thought about adding a whole section at the bottom (or other place), called 'announcements', or 'plans', or 'upcoming' or whatever11:55
wolfspraulbut then I can never convince myself to actually write something there11:56
wpwrak_yeah, but people many still want to know about the workshop :)11:57
wpwrak_unlike the typical roadmap item, it's something with a pretty definite schedule :)11:57
wolfspraulyes I understand, my total refusal to talk about upcoming things is also not good11:57
wolfspraulotherwise you always find out about things too late11:58
wolfspraulgood point11:58
wolfspraulmaybe if it's a fixed date, it should be mentioned11:58
wpwrak_more importantly, if you don't know it before, you'll miss it11:58
wolfspraulI'm not a news person, in general I am very reluctant about 'upcoming' stuff but of course we should have better criteria than that for what is 'good' upcoming stuff and what not.12:00
wolfspraulmaybe if it has a fixed date in the calendar, that's a very good indicator it should be mentioned12:00
wpwrak_with a product announcement, it's okay if you learn about it after the fact. well, unless you plan on spending the night before the launch waiting in the line outside the shop :)12:01
wolfsprauland if nobody is willing to put a date next to whatever is announced or upcoming, then maybe it shouldn't be in12:01
wpwrak_hehe :)12:01
wolfspraulyes I definitely understand the power of announcements, but that's why I am reluctant12:01
wolfspraulit adds an extra burden12:01
wolfspraulanyway, I like the 'fixed date' criteria12:02
wolfspraulI'll keep it in mind... thanks!12:02
wpwrak_i think there aren't that many events that need announcing. stuff like public talks and such.12:02
wpwrak_hmm, let's make it "fixed date" plus "you have to know about it before to make the most out of it"12:03
wpwrak_then you don't have to worry about more-or-less-fixed product launch dates and such (well, unless you want to :)12:03
wpwrak_or perhaps two levels: the ones with a fixed expiration date, should always go in, the ones with a date that can be missed are optional12:04
wpwrak_regarding the news, if you intend this as a channel also to keep the press updated, particularly events like the workshop are important. otherwise, they may miss it, and then it doesn't get covered in the probably widely read report on the CCC event.12:06
wpwrak_hmm. seems that i need to power cycle the usrp every now and then, or it starts measuring junk :-(14:10
wpwrak_wow ! it's the bloody ground vias !15:22
kristianpaulgood, how do you find it?15:43
wpwrak_kristianpaul: looked for texts on f-antennas to see if i had any flaws in my logic. then i found one where they said the vias had to be 50 mil apart. mine are 200 mil. reworked one of the antennas, measured it. lo and behold ...15:54
wpwrak_now .. rework of the other nine boards ... i'll skip the three with a negative size change. they were just the control group.16:27
virichummm qucs does not build with gcc 4.5.116:52
viricspfile.cpp:405:21: error: call of overloaded 'conj(nr_complex_t)' is ambiguous16:52
kristianpaulbe carefull lekernel could heard you ;)16:53
viricwould that help? :)16:53
kristianpaulno actually17:05
kristianpaultry askign #gcc17:06
virickristianpaul: I imagine it's a qucs bug, not a gcc bug :)17:21
kristianpaulahh i tought17:21
kristianpaulnv then17:21
wpwrak_that sort of thing is actually quite common with c++. the language seems to have an incredibly fast bit-rot.17:28
kristianpaulNow is the time to GMU20:41
kristianpaulindeed font is TOO small20:41
qi-bot[commit] Xiangfu Liu: automatic create /dev/rtc http://qi-hw.com/p/openwrt-xburst/f10460321:02
kristianpaultuxbrain: hi21:35
kristianpaultuxbrain: are you aware of skins and got setting for gmu?21:36
kristianpaulahh moc is not in owrt21:37
kristianpaulmpd is there but i requires a fronted anyway21:38
wolfspraulwhat is moc?21:39
kristianpauland ncurses music player21:41
kristianpauli use it is fast and dint get freeze like others21:41
kristianpaulbtw in the meant time kexec can replace uboot, how hard is get a silent uboot boot, i wonder if all those prints are also tooo infomartives and delay some  bootime..21:44
kristianpauli a tought21:44
kristianpaulis just*21:44
wpwrak_uboot is fairly silent. are you sure you don't mean kernel messages ?21:45
wpwrak_if i remember right, you can suppress them with the boot parameter "quiet"21:45
kristianpaulbefore load kernel21:45
kristianpaulwhen it is looking for /boot/uImage21:46
wpwrak_ah, uSD. haven't tried that yet :)21:46
kristianpaulno no21:46
kristianpauleven from flash21:46
kristianpaulis same tought21:46
wpwrak_wolfspraul: btw, you once mentioned that you got some breakout cables made as a "street job". did this actually happen or was it just an idea that's still awaiting implementation ?21:47
kristianpaulwell long dat i'm off bed21:47
wolfspraulkristianpaul: what is the source url for moc?21:53
wolfspraul[cables] yes sure I made 1021:53
wolfspraulwill give them away here and there when there is an opportunity21:53
wolfspraulfuse is there, inductor forgotten :-)21:54
wpwrak_wolfspraul: kewl ! you should post about them. even more news :-)21:54
kristianpauluSD to gpio cables?21:54
kristianpaulohh http://moc.daper.net/node/73621:55
kristianpaulalready there!21:55
kristianpaulxiangfu: http://pastebin.com/DTbgiJi021:55
wpwrak_wolfspraul: and maybe something distributors might be interested in as well ... at least tuxbrain sounded very excited about this back then21:55
kristianpaulcached http://ur1.ca/21:56
Action: kristianpaul zzzZ21:56
wpwrak_kristianpaul: let's see how long we can keep you awake ;-)21:57
--- Thu Dec 2 201000:00

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