2010-12-01 00:11 wpwrak_: ok I cleaned it up a bit... http://en.qi-hardware.com/wiki/Community_news_2010-12-01 2010-12-01 00:14 xiangfu: there is an error report for fped at Debian, see http://qa.debian.org/developer.php?login=xiangfu%40sharism.cc 2010-12-01 00:19 wolfspraul: don't understand the error. will ask debian people. in #debian-mentor 2010-12-01 00:20 good 2010-12-01 00:23 form the #debian-mentor: 2010-12-01 00:23 since upstream doesn't do releases, just ignore it 2010-12-01 00:23 or poke upstream to have proper software development practices 2010-12-01 00:28 I'm sure Werner will love that... 2010-12-01 00:28 [commit] Xiangfu Liu: update the homepage to help webpage http://qi-hw.com/p/fped/5a5bc8c 2010-12-01 00:41 but if you put the wan if into the right zone it should just work 2010-12-01 00:42 irgh 2010-12-01 01:57 xiangfu: 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.patch 2010-12-01 01:57 xiangfu: would be great if you could test 2010-12-01 01:57 kyak: thanks. I will test it. 2010-12-01 02:27 kyak: great. works pretty good. 2010-12-01 02:29 good. i'll commit then? 2010-12-01 02:31 kyak: yes. 2010-12-01 02:33 [commit] kyak: reflash_ben.sh: add progress bar http://qi-hw.com/p/openwrt-xburst/5cb8088 2010-12-01 02:34 i thougth the next step could be to output the spent time/ left time, but i noticed that the transfer is somwhat not continous 2010-12-01 02:34 i.e. it transfer 16 times, then it waits for somethinfg 2010-12-01 02:35 so maybe better leave it like it is.. at least now we have an impression how much is left to reflash 2010-12-01 02:35 kyak: yes. sure. 2010-12-01 02:36 xiangfu: do you know why it works like this? i.e. transferring 16 times, then waits 2010-12-01 02:39 kyak: i am not sure.  it's PIPO issue. 2010-12-01 02:40 (guess) only the PIPO is full or EOF, then "tee" will send message out. 2010-12-01 02:40 PIPO,, have to google that 2010-12-01 02:40 sorry FIFO 2010-12-01 02:40 :) 2010-12-01 02:40 ah 2010-12-01 02:40 no, it's not tee 2010-12-01 02:41 it's really what happens 2010-12-01 02:41 you can start tail -f log.txt in once console and reflash_ben.sh (previous version) in another 2010-12-01 02:41 you'll see this thing 2010-12-01 02:42 you'll see that it really waits between these series of 16 blocks 2010-12-01 02:42 or whatever it is 2010-12-01 02:42 i never really noticed it before 2010-12-01 02:43 before i watched this process with a progress bar 2010-12-01 02:43 I know that. only when we use script file , the log.txt will like that. 2010-12-01 02:44 so 'shell' must cache the output. 2010-12-01 02:45 need someone really understand the 'shell' can answer this question. I am not sure. 2010-12-01 02:45 then the script itself has a problem? 2010-12-01 02:46 i'll try launching it without the script.. i.e. just the nprog 2048 ${WORKING_DIR}/${ROOTFS} 0 0 -n (from usbboot console) 2010-12-01 02:46 the script file it's like: "3>> "${LOG_FILE}" 2>&1 >&3" 2010-12-01 02:46 i wonder what i'll see nprog 2048 ${WORKING_DIR}/${ROOTFS} 0 0 -n 2010-12-01 02:46 i wonder what i'll see in this case 2010-12-01 02:46 if it will be a continous output 2010-12-01 02:47 which i doubt 2010-12-01 02:47 i know how it was before in script file.. i spend pretty much time trying to figure out that "3>> "${LOG_FILE}" 2>&1 >&3" thing 2010-12-01 02:47 kyak, direct run "usbboot ...". the output will continue. 2010-12-01 02:47 then the script has a bug 2010-12-01 02:51 it's ok that the script writes to the log file after some caching.. but things going to stdout must be instant 2010-12-01 02:56 kyak: there is some code "usleep(100);, sleep(1)" in usbboot.  is that the problem ?? 2010-12-01 02:57 xiangfu: i'm not sure.. i can't test the usbboot right now -\ 2010-12-01 02:57 but the delay is more than 1 second 2010-12-01 02:58 i suspect that usbboot might be delaying it's output 2010-12-01 02:58 or waiting for something 2010-12-01 02:58 but it is needed to be tested outside th escript 2010-12-01 03:00 when direct run "usbboot". the output just fine. no delay at all. ( I always direct run "usbboot") 2010-12-01 03:00 oh ok.. 2010-12-01 03:01 it's hard to judge though, because the lines are the same all the time 2010-12-01 03:01 at some point it may appear that the screen is not changing at all 2010-12-01 03:04 in my test script, there is no delay 2010-12-01 03:04 that's why my assumption is that it is coming from usbboot 2010-12-01 03:06 basically the test script is the same, only there is another script that simualtes usbboot output 2010-12-01 03:06 can you send the test script files to me. 2010-12-01 03:06 one sec 2010-12-01 03:07 http://downloads.qi-hardware.com/people/kyak/tmp/reflash.sh 2010-12-01 03:08 http://downloads.qi-hardware.com/people/kyak/tmp/progress.sh 2010-12-01 03:08 the reflash.sh simualtes usboot output 2010-12-01 03:08 you run progress.sh 2010-12-01 03:08 if there is not delay in reflash.sh output, there is no delay in progress.sh indication 2010-12-01 03:10 you can customize the delay and number of blocks to "write" in reflash.sh 2010-12-01 03:17 kyak: strange. don't know why. :( 2010-12-01 03:19 xiangfu: btw, the usbboot - is it written by qi, or is it from ingenic? 2010-12-01 03:20 kyak: by Qi: http://projects.qi-hardware.com/index.php/p/xburst-tools/source/tree/master/ 2010-12-01 03:21 oh, great.. at least we have a full control over all of those things 2010-12-01 03:21 (i still rememeber triggerhappy) :) 2010-12-01 04:09 xiangfu, wolfspraul: (fped error) so .. no action required ? :) 2010-12-01 04:11 wolfspraul: (wpan antenna) btw, here's a picture of my antenna farm: http://downloads.qi-hardware.com/people/werner/tmp/antfarm.jpg 2010-12-01 04:11 original: http://downloads.qi-hardware.com/people/werner/tmp/IMG_0661.JPG 2010-12-01 04:14 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" 2010-12-01 04:14 wolfspraul: (mm1) how about mentioning that the case parts were laser-cut ? 2010-12-01 04:18 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." 2010-12-01 04:20 ha :-) 2010-12-01 04:20 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." 2010-12-01 04:23 hmm, too bad that jlime didn't make it into this news batch 2010-12-01 04:24 don't know what exactly the news is there, someone just needs to write it up 2010-12-01 04:28 (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) 2010-12-01 04:31 ah ... maybe "upcoming events": the MM1 workshop at CCC ! 2010-12-01 05:13 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. 2010-12-01 05:15 http://downloads.qi-hardware.com/people/werner/wpan/tmp/ants-s1-weird-change.png 2010-12-01 05:16 the tree that drop to ~ -31.5 dB around 2440 MHz. that's not a normal curve. 2010-12-01 05:19 oops. make that http://downloads.qi-hardware.com/people/werner/wpan/tmp/ants-s2-weird-change.png 2010-12-01 05:21 grmbl. one the antennas that tested okay before now also acts weird :-( 2010-12-01 05:26 [commit] Xiangfu Liu: move ks7010 firmware to it's package http://qi-hw.com/p/openwrt-xburst/0403a6a 2010-12-01 05:51 [commit] Xiangfu Liu: move those example file to a new package: nanonote-example-files http://qi-hw.com/p/openwrt-xburst/4e3b2db 2010-12-01 06:00 [commit] Xiangfu Liu: new package, nanonote example files package http://qi-hw.com/p/openwrt-packages/ca85c07 2010-12-01 06:12 intersting ... power-cycle all devices, reconnect antenna. voila, signal is some 15 dB stronger than before. WFT ?!? :-( 2010-12-01 06:13 it does look a lot "cleaner", though. i wonder what happened before. 2010-12-01 06:38 [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/d170cb7 2010-12-01 06:43 wpwrak_: (scope) no, i also used some multimeters, PSU 2010-12-01 06:44 wpwrak_: they also had an spectrumanalizer but i dint used at last 2010-12-01 06:45 mirko: they DO compile 2010-12-01 06:45 they require locale to be enabled 2010-12-01 06:45 therefore patch for fbterm was removed 2010-12-01 06:46 you might be missing one of the commits to openwrt-xburst 2010-12-01 06:47 1b577b72608d4cd16de089a5d8eee419cf9ab4b2 this one, to be specific 2010-12-01 06:47 wpwrak_: (ants) weird changed indeed, your finding could be interesting for nokia ;) 2010-12-01 06:48 kyak: hmm, did i miss to update the qi-packages repo first? (thinking...) 2010-12-01 06:48 actually it looks like more the oposite signal 2010-12-01 06:49 "oposite" or english equivalent 2010-12-01 06:49 mirko: well, if both openwrt-packages and openwrt-xburst are updated to the latest master, they compile 2010-12-01 06:50 it is 2010-12-01 06:50 updated and started the full build yesterday 2010-12-01 06:53 updated both repos to latest HEAD, re-enabled them and will test again 2010-12-01 06:54 and your feeds.conf are using the latest version of qi-packages? 2010-12-01 06:54 yes 2010-12-01 06:55 ok then.. pretty strange though because xiangfu also didn't complain 2010-12-01 06:56 mirko: are you building from scratch? 2010-12-01 06:56 yes 2010-12-01 06:57 kristianpaul: (nokia) hmm, i think they know RF a lot better than in could every hope to ;-) 2010-12-01 06:58 wpwrak_: sure just kidding 2010-12-01 08:10 hmm 2010-12-01 08:40 [commit] carlos: Adding PS2, capacitive keyboard examples http://qi-hw.com/p/nn-usb-fpga/62d0edf 2010-12-01 09:10 [commit] Werner Almesberger: atusb: use 0402 as the preferred component size and replace bad TVS http://qi-hw.com/p/ben-wpan/23c3726 2010-12-01 09:10 [commit] Werner Almesberger: usrp/README: change threshold to avoid making section reference look like a typo http://qi-hw.com/p/ben-wpan/fea4ee5 2010-12-01 09:10 [commit] Werner Almesberger: usrp: try to bring back sanity to pre- and post-processing of FFT data http://qi-hw.com/p/ben-wpan/40d1234 2010-12-01 09:10 [commit] Werner Almesberger: ants/cam: update for latest workpiece http://qi-hw.com/p/ben-wpan/04972bb 2010-12-01 09:10 [commit] Werner Almesberger: usrp: update filtering and display for uncorrupted measurement setup http://qi-hw.com/p/ben-wpan/b3c0b4b 2010-12-01 09:10 [commit] Werner Almesberger: usrp/doall: usage and allow passing of arguments to evscan as well http://qi-hw.com/p/ben-wpan/e52b92f 2010-12-01 09:10 [commit] Werner Almesberger: usrp/range: more useful diagnostic output and harden against underflows http://qi-hw.com/p/ben-wpan/8ea1715 2010-12-01 09:10 [commit] Werner Almesberger: atusb: updated footprint assignment http://qi-hw.com/p/ben-wpan/9ad0609 2010-12-01 09:10 [commit] Werner Almesberger: atusb/cam: modernize, and change setup for current workpiece http://qi-hw.com/p/ben-wpan/e137bc4 2010-12-01 11:33 [commit] Werner Almesberger: atusb: remove two unnecessary test points http://qi-hw.com/p/ben-wpan/521dab8 2010-12-01 11:37 wolfspraul: you did it ! congratulations !! 2010-12-01 11:39 the news? yeah 2010-12-01 11:39 done 2010-12-01 11:39 I could have mentioned the Milkymist One RC2 production, forgot... but also no tangible enough results yet 2010-12-01 11:43 (mm1) you could have mentioned the upcoming workshop 2010-12-01 11:44 (i wrote this before. not sure if you saw it.) 2010-12-01 11:55 I don't like 'upcoming' stuff 2010-12-01 11:55 so I don't add it :-) it's a wiki... 2010-12-01 11:55 a few times I thought about adding a whole section at the bottom (or other place), called 'announcements', or 'plans', or 'upcoming' or whatever 2010-12-01 11:56 but then I can never convince myself to actually write something there 2010-12-01 11:57 yeah, but people many still want to know about the workshop :) 2010-12-01 11:57 unlike the typical roadmap item, it's something with a pretty definite schedule :) 2010-12-01 11:57 yes I understand, my total refusal to talk about upcoming things is also not good 2010-12-01 11:58 otherwise you always find out about things too late 2010-12-01 11:58 good point 2010-12-01 11:58 maybe if it's a fixed date, it should be mentioned 2010-12-01 11:58 more importantly, if you don't know it before, you'll miss it 2010-12-01 11:59 sure 2010-12-01 12:00 I'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. 2010-12-01 12:00 maybe if it has a fixed date in the calendar, that's a very good indicator it should be mentioned 2010-12-01 12:01 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 :) 2010-12-01 12:01 and if nobody is willing to put a date next to whatever is announced or upcoming, then maybe it shouldn't be in 2010-12-01 12:01 hehe :) 2010-12-01 12:01 yes I definitely understand the power of announcements, but that's why I am reluctant 2010-12-01 12:01 it adds an extra burden 2010-12-01 12:02 anyway, I like the 'fixed date' criteria 2010-12-01 12:02 I'll keep it in mind... thanks! 2010-12-01 12:02 i think there aren't that many events that need announcing. stuff like public talks and such. 2010-12-01 12:03 hmm, let's make it "fixed date" plus "you have to know about it before to make the most out of it" 2010-12-01 12:03 then you don't have to worry about more-or-less-fixed product launch dates and such (well, unless you want to :) 2010-12-01 12:04 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 optional 2010-12-01 12:06 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. 2010-12-01 14:10 hmm. seems that i need to power cycle the usrp every now and then, or it starts measuring junk :-( 2010-12-01 14:32 hmm? 2010-12-01 15:22 wow ! it's the bloody ground vias ! 2010-12-01 15:43 good, how do you find it? 2010-12-01 15:54 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 ... 2010-12-01 16:27 now .. rework of the other nine boards ... i'll skip the three with a negative size change. they were just the control group. 2010-12-01 16:52 Hep 2010-12-01 16:52 hummm qucs does not build with gcc 4.5.1 2010-12-01 16:52 spfile.cpp:405:21: error: call of overloaded 'conj(nr_complex_t)' is ambiguous 2010-12-01 16:52 annoying 2010-12-01 16:53 be carefull lekernel could heard you ;) 2010-12-01 16:53 would that help? :) 2010-12-01 17:05 no actually 2010-12-01 17:06 try askign #gcc 2010-12-01 17:21 kristianpaul: I imagine it's a qucs bug, not a gcc bug :) 2010-12-01 17:21 ahh i tought 2010-12-01 17:21 nv then 2010-12-01 17:28 that sort of thing is actually quite common with c++. the language seems to have an incredibly fast bit-rot. 2010-12-01 20:41 Now is the time to GMU 2010-12-01 20:41 indeed font is TOO small 2010-12-01 21:02 [commit] Xiangfu Liu: automatic create /dev/rtc http://qi-hw.com/p/openwrt-xburst/f104603 2010-12-01 21:35 tuxbrain: hi 2010-12-01 21:36 tuxbrain: are you aware of skins and got setting for gmu? 2010-12-01 21:37 ahh moc is not in owrt 2010-12-01 21:38 mpd is there but i requires a fronted anyway 2010-12-01 21:38 anyway.. 2010-12-01 21:39 what is moc? 2010-12-01 21:41 and ncurses music player 2010-12-01 21:41 i use it is fast and dint get freeze like others 2010-12-01 21:41 http://screenshots.debian.net/package/moc 2010-12-01 21:44 btw 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.. 2010-12-01 21:44 i a tought 2010-12-01 21:44 is just* 2010-12-01 21:45 uboot is fairly silent. are you sure you don't mean kernel messages ? 2010-12-01 21:45 if i remember right, you can suppress them with the boot parameter "quiet" 2010-12-01 21:45 ahh 2010-12-01 21:45 no 2010-12-01 21:45 before load kernel 2010-12-01 21:46 when it is looking for /boot/uImage 2010-12-01 21:46 ah, uSD. haven't tried that yet :) 2010-12-01 21:46 no no 2010-12-01 21:46 even from flash 2010-12-01 21:46 is same tought 2010-12-01 21:47 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 ? 2010-12-01 21:47 well long dat i'm off bed 2010-12-01 21:47 bye 2010-12-01 21:48 s/dat/day 2010-12-01 21:53 kristianpaul: what is the source url for moc? 2010-12-01 21:53 [cables] yes sure I made 10 2010-12-01 21:53 will give them away here and there when there is an opportunity 2010-12-01 21:54 fuse is there, inductor forgotten :-) 2010-12-01 21:54 http://moc.daper.net/ 2010-12-01 21:54 wolfspraul: kewl ! you should post about them. even more news :-) 2010-12-01 21:54 uSD to gpio cables? 2010-12-01 21:55 ohh http://moc.daper.net/node/736 2010-12-01 21:55 already there! 2010-12-01 21:55 xiangfu: http://pastebin.com/DTbgiJi0 2010-12-01 21:55 wolfspraul: and maybe something distributors might be interested in as well ... at least tuxbrain sounded very excited about this back then 2010-12-01 21:56 cached http://ur1.ca/ 2010-12-01 21:56 zzzZ 2010-12-01 21:57 kristianpaul: let's see how long we can keep you awake ;-)