#qi-hardware IRC log for Saturday, 2010-12-18

wolfspraulfor the --order parameter in schhist, are those file names or KiCad strings for the schematic pages?00:02
wpwrakhmm, good question ...00:02
wolfspraulno problem I check it00:03
wolfspraulfor the order of pages, I propose to start with the overview page xue-rnc00:03
wolfspraulafter that the 2 fpga pages, port0/2, then 1/300:03
wolfspraulI wouldn't want to rip those 2 fpga pages apart00:03
wpwrakfile names without extension (i think :)00:04
wpwrakyup, start with overview is good00:04
wolfspraulthen ddr, then 'non volatile memories'00:04
wolfspraulor maybe the psu first right after the fpga, or even before the fpga?00:05
wpwrakbefore everything sounds nice, considering how often it is accessed00:05
wolfspraulI think fpga first (both pages), then ddr, then nvram, then psu, then usb/ethernet/expansion, finally sensor and sensor_psu00:05
wolfspraulok, psu first then00:06
wolfspraulthen we do this:00:06
wolfsprauloverview, psu, fpga1, fpga2, nvram, ddr, ethernet, usb, expansion, sensor_psu, sensor00:06
wolfspraulI will insert this strange dbg_prg after the psu for now, it will probably be deleted later anyway00:07
wpwrakyeah :)00:09
qi-bot[commit] Wolfgang Spraul: testing schhist heuristics p1: expantion.sch renamed to epansion.sch http://qi-hw.com/p/xue/38a326e00:19
wolfspraulI'll do this slowly, and see how schhist reacts (I started a clean run, so need to wait a little)00:19
wolfspraulwpwrak: should we name the ddr page ddr or sdram? or ddr-sdram?00:26
wolfspraulI'm leaning towards sdram, but maybe 'ddr' is more eye-popping.00:26
wpwrakram ? ;-)00:26
wolfspraulwell we have nvram already00:26
wolfspraulnon volatile00:26
wolfspraulso another one 'sdram' (synchronous) seems ok00:26
wpwrakbut there's no nvRAM :)00:26
wolfspraulddr is still sdram00:26
wpwrakthere's a lot of flash, though :)00:27
wolfspraulno objections against sdram?00:27
wpwraksure, no problem00:27
wolfspraulfine I'll name that one flash then00:27
wolfspraulyou are right that non volatile random access memory is wrong in the first place00:27
wolfspraulso flash, sdram00:28
wolfspraulright now it's called 'non volatile memories', I introduced the 'ra' inaccuracy00:28
wpwraktsk tsk :)00:29
wolfspraulshould I shorten ethernet to just eth?00:30
wolfspraulyeah unless there are complaints I'll do that...00:31
wpwraki like short names :) ether also works00:38
wpwrakafk for a bit - dinner00:39
qi-bot[commit] Wolfgang Spraul: USB.sch -> usb.sch http://qi-hw.com/p/xue/e81945900:44
qi-bot[commit] Wolfgang Spraul: NV_MEMORIES.sch -> flash.sch http://qi-hw.com/p/xue/ccaece900:44
qi-bot[commit] Wolfgang Spraul: PSU.sch -> psu.sch http://qi-hw.com/p/xue/68f042500:44
qi-bot[commit] Wolfgang Spraul: DRAM.sch -> sdram.sch http://qi-hw.com/p/xue/eb9b37b00:44
wolfspraulether is good, thx00:44
wolfspraulbut I will change sensor to cmos_image_sensor, it's better than cis because cis is not widely known00:44
wolfspraulenjoy dinner00:45
wpwrakcamera ?00:45
wolfspraulcis is correct00:45
wolfspraulbut not widely known00:45
wolfspraulyou want camera?00:45
wpwrakcamera would be intuitibvely clear even if a little incorrect00:45
wolfspraulcamera is also nice00:46
wolfspraulyes I agree00:46
wolfspraulthat's more important here00:46
wolfspraulnobody will know cis00:46
wolfsprauland cmos_image_sensor is too complicated00:46
wolfspraulgood idea, thx!00:46
wolfspraulpoor schhist00:46
wolfspraulwhen you are back there will be a bloodbath00:46
qi-bot[commit] Wolfgang Spraul: eth_phy.sch -> ether.sch http://qi-hw.com/p/xue/1bae64c00:59
qi-bot[commit] Wolfgang Spraul: sensor.sch -> camera.sch http://qi-hw.com/p/xue/1e72d6600:59
qi-bot[commit] Wolfgang Spraul: sensor_psu.sch -> camera_psu.sch http://qi-hw.com/p/xue/2e024d400:59
qi-bot[commit] Wolfgang Spraul: DBG_PRG.sch -> dbg_prg.sch http://qi-hw.com/p/xue/980427600:59
qi-bot[commit] Wolfgang Spraul: FPGA_0_2_PROG.sch -> fpga1.sch http://qi-hw.com/p/xue/655edaf00:59
qi-bot[commit] Wolfgang Spraul: FPGA_1_3.sch -> fpga2.sch http://qi-hw.com/p/xue/4e0ed9a00:59
qi-bot[commit] Wolfgang Spraul: removed 4 generated and temporary/local files http://qi-hw.com/p/xue/82891cc01:12
qi-bot[commit] Wolfgang Spraul: renamed 'DDR Banks' string to sdram http://qi-hw.com/p/xue/44837ea01:12
wpwrakso far, so good :)01:15
wolfspraulno the last one is not good01:20
wolfspraulI renamed the string of sdram.sch, the string from xue-rnc.sch01:21
wolfspraulI changed it from "DDR Banks" to "sdram"01:21
wolfspraulthe history now shows a deletion and creation of a new page01:21
wpwrakyup. it currently tracks one both not both names. that's what i meant when i said that it'll break in one way or another.01:22
wolfspraulhmm. why does it care about the string name at all? since it follows .sch file renames, that should be enough, no?01:28
wolfspraulthere's a -f switch to do just that :-)01:30
wpwrakif i recall right, xue had some file renaming in the past, that's why the heuristics are like they are01:30
wpwraklet's see what happens with -f :) if my memory is correct, some other problem should then pop up :)01:31
wolfspraulI think the -f documentation is wrong, it says 'identify sheets by their file name, not the sheet name'01:31
wolfspraulbut reading the sources I think it's the other way round01:31
wolfspraulah wait, no, I'm confused01:32
wpwrakah yes. it's what goes into the title01:33
wpwraki added it for one of the student projects, which had some ugly semi-binary stuff in the name01:33
wpwrak(some temporary name kicad assigns by default, i guess)01:33
wolfspraulI added -f but I suspect we now get some other breakage01:35
wolfspraulbecause when the project was still called CHIE they probably did not use proper git mv to rename the files01:35
wolfspraulbut instead they deleted and readded them under new names.01:35
wpwraki think this is the same for git01:36
wpwrakits rename detection is based on looking for new files that are similar to deleted files :)01:36
wolfspraulgit will record a rename/move01:36
wolfspraulmaybe it has that in addition somewhere, but I'm pretty sure it has genuine support for move/rename01:36
wpwraki think it doesn't record it but tries hard to report a delete/add pair as a rename :)01:37
wolfspraulstrange, I am still confused in schhist2web01:41
wolfspraul-f says "identify sheets by their file name"01:41
wolfsprauldefault is false01:41
wolfspraulwhen -f is set it becomes true01:41
wpwrakdid you run with -f ?01:42
wolfspraulin line 265, it says elif $use_sch_name && ... subschname2file ...01:42
wolfspraulso if use_sch_name is true, it calls subschname2file01:42
wolfspraulsubschname2file will look for F0 (the name string), so it's the one that goes from a string name to a file name01:43
wolfspraulI'm misreading something somewhere01:43
wolfspraulbefore I ran without -f. -f was only used for SIE_CEIMTUN01:44
wolfspraulnow I'm rerunning with -f just to see how it looks01:44
wolfspraulmeanwhile I'm reading the script trying to understand what it is doing01:45
wolfspraulmaybe we only need to introduce an else case in 27601:46
wolfspraulline 27601:46
wpwrakhmm .. lemme think ...01:48
wpwraklet's see what -f yields. i'm not entirely sure anymore about what failure mode to expect01:51
wpwrakit may pass, but use "ugly" names01:52
wpwrakbut maybe there's something else i'm not thinking of at the moment01:52
wolfspraulam I misunderstanding -f ?01:52
wolfspraulthe documentation and what I read in the script do not match01:53
wolfspraulmaybe I misunderstand the syntax somewhere?01:53
wolfspraul && continues when the left side is true01:53
wolfspraulif it is false, it aborts. right?01:53
wolfspraulso if -f is set, it will go to the subsch2name script, which uses the string name to lookup the file name01:54
wolfspraulbut the -f docu says 'identifies by their file name'?01:54
wolfspraulintroducing an else case in 276 is probably a good idea, no reason to give up there01:55
wolfspraulbut let's see...01:55
wpwrakit takes the "string name" to get the file name. then it continues working with the file name01:57
wpwrakbefore it used the "string name" to identify the sheet01:57
wolfspraulbut the -f documentation says the opposite01:58
wolfspraul"identify sheets by their file name, not the sheet name"01:58
wolfsprauldon't you think it's "identify sheets by their sheet name, not the file name"?01:58
wolfspraulactually it looks like "identify sheets by their sheet name, if file name not found"01:58
wolfspraulbecause this only kicks in when the file name is not found, if I see correctly01:59
wolfspraulif this is true, there should be no reason to not make -f the default02:00
wpwrakthe first check is for the root sheet02:00
wpwrakthe root sheet is special02:01
wpwrakfor the others, we come from the .ps files. kicad uses the "string name" for the .ps files, not the .sch file's name02:01
wpwrak(not my idea ;-)02:02
wolfspraulI will make the two the same, once we can avoid schhist breaking down...02:02
wolfspraulso the file name is the sheet name, at this place02:02
wpwraksheet name = foo.sch or the thingy inside foo.sch ?02:04
wpwraklet's say we have foo.sch which calls itself (inside) "bar"02:05
wpwrakhow we get some project-bar.ps ("project" is the basename of the top-level sheet, project.sch)02:05
wpwrakthen we check if foo.sch happens to be project.sch02:06
wpwrakerr, sorry02:06
wpwrakwe check if "bar" happens to be "project"02:06
wpwrakif it is, then we're looking at the top-level sheet. we track top-level sheets elsewhere, so we already know we're good (else we wouldn't have made it this far)02:07
wpwraknow, if -f isn't set, we just use "bar"02:07
wpwrakotherwise, we dig a little deeper - and try to obtain the real file name, in this case foo.sch02:08
wpwraknow, through all this, we're at some point in the project's history02:09
wpwrakwith the name foo.sch, we have something git can relate to. so we ask it for the latest name of this file, considering all the renames that may have happened since. this is what gitwhoareyounow does.02:10
wpwrakfinally, we use "foo" or any "foo-today" git may have found as our name of the sheet02:11
wolfspraulgood thing this is logged for eternity02:13
wolfspraulif I need to go back in there I will paste it as comments, still waiting for -f results02:14
wolfspraulwpwrak: wow nice!02:27
wolfspraul-f is magic :-)02:27
wpwrakwhee ! :)02:27
wpwraknow that the names are "nice", it looks quite decent02:28
wolfspraulok I will continue to fix the strings, hopefully that won't break schhist again02:29
wolfspraulmaybe -f should be the default? well, for now we are good...02:29
wpwrakmaybe do it all in one commit, to avoid this long string of changes in the history02:29
wpwrakif the file names are useful (which they are now), -f is good02:30
qi-bot[commit] Wolfgang Spraul: fixed FPGA GIOS -> expansion string http://qi-hw.com/p/xue/a1bc1f402:35
qi-bot[commit] Wolfgang Spraul: fixed Image Sensor -> camera string http://qi-hw.com/p/xue/431332d02:35
qi-bot[commit] Wolfgang Spraul: fixed Snesor PSU -> camera_psu string http://qi-hw.com/p/xue/cc1268802:35
qi-bot[commit] Wolfgang Spraul: fixed fpga1 string http://qi-hw.com/p/xue/26d165e02:35
qi-bot[commit] Wolfgang Spraul: fixed fpga2 string http://qi-hw.com/p/xue/cfa930502:35
qi-bot[commit] Wolfgang Spraul: fixed dbg_prg string http://qi-hw.com/p/xue/c6dbc8e02:35
qi-bot[commit] Wolfgang Spraul: fixed psu string http://qi-hw.com/p/xue/965f69e02:35
qi-bot[commit] Wolfgang Spraul: fixed flash string http://qi-hw.com/p/xue/077c29d02:35
wolfspraulsorry read your '1 commit' thing too late02:35
wolfspraulwho knows, separate commits can be helpful one day02:35
wolfspraulI am thinking about renaming xue-rnc to 'overview' but still hesitating a bit :-)02:36
wpwrakxue.sch ? :)02:36
wpwrak(separate commits) each will generate a line in the graphical history. so now you have to page down a looong way :)02:37
wolfsprauleven those?02:39
wolfspraulthe ones before did, not sure about those02:39
wolfspraulah yes, you are right02:39
wolfsprauloh well02:39
wpwrakboth names appear in the top-level sheet, so each triggers a diff line02:39
wolfspraulI can go in, delete the history, and redo it all in 1 commit02:41
wolfspraulit seems schhist should be able to handle that, so maybe I try...02:41
wpwrakyes, rewriting history would compact them02:42
wolfspraulI did a git rebase and squashed it all into 1 commit locally. can I just git push this now?02:56
wpwraki think git will auto-create a merge commit between the current history and your rebase03:00
wpwraknot sure which path schhist will travel03:01
wpwrakthere must be a wait to push a rebase without the merge commit (after all, that's what andy did at openmoko), but i don't know how.03:02
wpwrakof course, rebases in published history are considered anti-social anyway ;-)03:03
wpwrakah, now the whole gang shows up :)03:04
qi-bot[commit] Wolfgang Spraul: renaming schematics pages http://qi-hw.com/p/xue/5dd9abe03:07
wolfspraulyes but I don't think anybody but you had any of those commits pulled, so let's see03:10
wolfsprauli'm rerunning schhist again now03:10
wolfspraulthis is a pretty hardcore commit now though, I hope we haven't made things worse03:12
wolfspraulit looked good before except for the 2 pages at the top03:12
wpwraki didn't pull them either :)03:14
wpwraklet's see what the history looks like now ..03:15
wpwrakah yes, single commit. nice.03:15
wolfspraulwpwrak: you mentioned Makefiles the other day (in the Xue tree)03:26
wolfspraulwhich ones did you have in mind?03:26
wolfspraulI'll just start doing them to speed things up03:26
wolfspraulI see another 4 cache files I will delete03:27
wolfsprauland I think the .net is the generated netlist which we can also delete03:27
wolfspraulthen we have xue-rnc.cmp, not sure about that one but it looks generated too03:28
wpwrakkeep .cmp03:29
wolfspraulhey, roh blogged about the next round of Milkymist One case work... https://m21.hyte.de/blog/mmone-case03:30
wpwrakthat's semi-generated. you get it when you associate the components with cvpcb03:30
wolfspraulok understood03:30
wolfspraulbut .net can go?03:30
wpwrak.net can go03:30
wpwrak.cmp may or may not be redundant. but in any case, if it's not there, something (pcbnew, i think) will complain all the time03:30
wolfsprauland the 4 cache files too, unless they accidentally moved original data in there (which I saw before, hope it's not the case here)03:30
wolfspraulsure we can cleanup slowly03:31
wpwrak(".cmp may or may not") what i mean is that it can be 100% redundant (if you set all the footprints in the schematics), but it can also contain original date (if the schematics don't have all the details or if you manually override them). so it's not generally safe to delete .cmp files.03:33
wolfspraulthe .sch files all list LIBS:xue-rnc-cache03:33
wolfspraulshould I remove that line from the .sch files? (together with the -cache file)03:33
wpwraki think this LIBS line is just some output that isn't of much use anyway03:33
wpwraki wouldn't bother :)03:34
wolfspraulyeah, a LIBS:-cache entry is in mmone-jtag-serial cable too03:34
wolfspraulok so I just delete the cach files from the repository first03:34
wpwrakit's just spam :)03:34
wolfspraulthat should be safe, and if not we need to rescue the original data from them03:34
qi-bot[commit] Werner Almesberger: bin/purge: revert KiCad .pro files in which only the timestamp changed http://qi-hw.com/p/wernermisc/9a3f87303:35
wpwrakspeaking of spam, you may like this one :)03:35
wolfspraulyeah horrible03:36
wolfspraultimestamp inside a file, bah03:36
wpwrakyeah, kill the caches03:36
wolfspraulI hope KiCad improves, steady and fast and powerful03:37
wpwrak(mm1 case) looks nice ! the top/bottom plates look a bit large, though. not sure how this comes across in real life.03:37
qi-bot[commit] Wolfgang Spraul: deleted backup, cache and generated files from repository http://qi-hw.com/p/xue/933c55803:37
wolfspraulI think that's mostly from the shadows03:38
wpwrakah, could be03:38
wolfspraulhow about Makefiles?03:38
wolfspraulwhich ones did you have in mind?03:39
wpwrakmakefile .. things like "make dsv", "make sch", "make brd"03:39
wpwrakautomate longish invocations03:39
wolfspraulwhat does make dsv do?03:39
wolfspraulmake dsv C103:39
wpwrakmake dsv  ->  dsv setup BOOKSHELF03:39
wolfspraulmake sch = eeschema top_schematics.sch03:39
wolfspraulok so we start with a simple Makefile in the root dir03:40
wpwraki would put one in root and one in kicad/xue-rnc/03:45
wolfspraulI'll start in root03:45
wpwrakalso for the .fpd files, a makefile would be handy (pick any of mine; modules/Makefile)03:46
wolfspraulouch, maybe I should not have deleted the cache files :-)04:13
wolfsprauloriginal stuff has creeped into them04:13
wpwrakthen find out what it was and make sure it gets found the proper way :)04:13
wpwraknice. schdiff even tells you want went wrong ;-)04:14
wolfspraulfirst I used my new drug04:16
wolfspraulmade the commit disappear from public history04:16
wolfspraulI suspected something like that already, had the same issue in mmone-jtag-serial-cable.04:17
wolfspraulthe KiCad UI seems to easily make people put original stuff into cache files. nice.04:17
wolfspraulI'll disect it...04:17
wpwrak(new drug) ;-)04:17
wpwrakIMHO, the whole kicad workflowis not very friendly to revision control and shared projects04:18
qi-bot[commit] Wolfgang Spraul: removed backup files and generated netlist http://qi-hw.com/p/xue/90179e005:12
qi-bot[commit] Wolfgang Spraul: removed two cache files http://qi-hw.com/p/xue/493444a05:12
qi-bot[commit] Wolfgang Spraul: added simple Makefile http://qi-hw.com/p/xue/8a5aeea05:12
qi-bot[commit] Wolfgang Spraul: reordered schematics pages http://qi-hw.com/p/xue/67098a205:27
qi-bot[commit] Wolfgang Spraul: rescued two components from cache library http://qi-hw.com/p/xue/547954e07:25
qi-bot[commit] Wolfgang Spraul: added brd target http://qi-hw.com/p/xue/6e6644b07:44
zrafahey.. i have a newbie wiki question07:44
zrafahow can I create a new wiki page? .. i am checking the menues at qi-hardware.com.. but i do not know how to create a new page07:45
wolfsprauljust search for it, then there should be a create option07:45
wolfsprauldo you see that?07:46
zrafaah.. let me try07:46
zrafayes, I see07:46
zrafawolfspraul: thanks a lot :)07:46
kristianpaulhmm qi-...com is not loading..08:10
kristianpaulah works now :)08:10
kristianpaulRRLP blog entry from Harald Welte blog plus commets from Dieter Spaar, are really helfull :)08:19
wolfspraulkristianpaul: you saw the nice m1 case already :-)08:22
wolfspraul(different subject)08:22
wolfspraulthe pieces are coming together, great!08:22
wolfspraulthis will be properly licensed and published of course, with process documentation and all...08:23
qi-bot[commit] Wolfgang Spraul: minor file cleanup (permissions, name, local files) http://qi-hw.com/p/xue/12e7b3e08:53
kristianpaulwolfspraul: (M1 case) yes, looks apropiated for a VJ Station :)08:55
kristianpaulccc is great event indeed :D09:02
lekernelkristianpaul: are you going to the ccc in the end?09:20
kristianpaullekernel: nope (no enougt funds)09:32
kristianpaulbut i'm buying a M1 soon :)09:32
lekernelkristianpaul: btw your in Colombia, right? do you know distributors who might be interested there?09:37
wolfspraulmaybe kristian paul will be our distributor09:38
lekernelyeah, that's an option too09:39
lekernelmy question didn't exclude him as distributor :)09:39
qi-bot[commit] Xiangfu Liu: add BenNanoNote to hosts file http://qi-hw.com/p/openwrt-xburst/170c1c409:57
kyakxiangfu: btw, i've given you a link some time ago, but i've ping timeouted :) http://qt-apps.org/content/show.php/kinyin?content=9592610:02
kyakmight be interesting for you and easy to port, too10:02
xiangfukyak: yes. thanks. I already start a little. not commit yet.10:03
kyakhow does chinese input work with latin keyboard?10:03
kyakis there some corrsepondence between chinese symbols and latin letters?10:04
xiangfukyak: sorry. what's the meaning of "corrsepondence ... "10:05
kyaksorry, i mean that latin characters are somehow mapped into chinese10:06
kyakhow do you remember that?10:06
xiangfukyak: I know to kind of chinese input. one is  base on "pronounce". another is base on the "the write of chinese character"10:06
xiangfuI know two.  [s/to/two]10:07
kyaki can understand the "pronounce". How does the "write of chinese character" work?10:08
xiangfukyak: like `}(ni hao) split to [»]  [] and [s] [P], chinese is  assemble by base small module. so easy latin mapped to several "base modules"10:11
xiangfukyak: like : http://www.wnwb.com/wnwb2005/images/wbzigen.gif10:12
kyakxiangfu: ah!i see now10:13
kyakso typing in chinese is more like typing sms on cell phone10:13
kyakwithout T9 :)10:13
xiangfukyak: so } --> [s] [P] -->  v b . when we type [vb], we will get a } :)10:13
kyakso these "base modules" cover all possible variants?10:14
xiangfukyak: there are some duplicates, it will come up wait for you select.10:16
kyakhttp://en.wikipedia.org/wiki/Chinese_input_methods_for_computers -very interesting10:17
kyakxiangfu: do you personally type a lot in CHinese?10:17
qi-bot[commit] David Kühling: fix DNS timeout problem when applications resolve the FQDN http://qi-hw.com/p/openwrt-xburst/13c25db10:18
qi-bot[commit] David Kühling: Merge branch 'master' of projects.qi-hardware.com:openwrt-xburst http://qi-hw.com/p/openwrt-xburst/5f9635310:18
xiangfukyak: yes. type a lot .10:18
kyakdo you type fast? :)10:19
xiangfukyak: I don't use pinyin. I use the other way.10:19
xiangfukyak: I practice a lot when I was in school . :)10:20
kyakcool :) which one do you use?10:20
xiangfukyak: I use this one : http://en.wikipedia.org/wiki/Wubi_method10:22
kyakit looks like you are not choosing an easy way :)10:23
xiangfukyak: when I start to learn type, the easy way is not easy in fact, but now. those input method can remember what you type. so it's a little intelligent.10:26
xiangfukyak: I think for now no one will try to study the WUBI.10:27
kyakthere are online web pages to try wubi :) pretty funny10:30
xiangfukyak: you know "Chinese" ??10:34
xiangfukyak: I mean you understand the "Chinese" ? then maybe we can talk in Chinese :)10:35
kyakno-no :)10:38
kyakxiangfu: i was just wondering how it works10:39
kyaknow i understand more or less10:39
xiangfukyak: ok.10:45
qi-bot[commit] Xiangfu Liu: new pakcage: http://qi-hw.com/p/openwrt-packages/2d8f0d611:24
xiangfukyak: time for sleep. see you.11:24
wpwrakhee haw ! 35% HCl solution + 28% peroxide solution. now i know why they use peroxide as rocket fuel ;-)11:25
wpwrak*whoosh* and the board it etched. takes something like a minute ;-)11:25
lekernelhehe, that's one of the things my mother had to suffer the sight of :)11:27
wpwraksuffer ? did you etch away the kitchen by accident ? :)11:28
lekernelthat and my lifter experiment that sparked and caught fire... hahaha11:28
lekernelno, but it did smell chlorine and nasty chemicals until I put that outside11:29
wpwrak"lifter" = mission to mars ?11:29
wpwrakoddly, there's no chloride smell. i just reused some etchant from yesterday, added the peroxide to make it reactive again (HCl+H2O2 gets stale very quickly. there's supposedly a more stable state further down that process, but it doesn't sound as much fun as the initial mix)11:31
lekerneldoesn't it get green?11:31
wpwrak(ionocraft) nice ! didn't know that ion propulsion was practical at the bottom of earth's gravity well11:33
wpwrakyup, it gets green. that11:34
wpwrak's the copper11:34
lekernelmh. mine was green right away because of the dissolved chlorine gas11:34
lekernel(or, at least, I guess so)11:34
lekernelwpwrak: not sure how practical that is; the device cannot lift its own power supply11:35
wpwrakthat would be quite a lot of gas11:35
lekernelit's pretty inefficient too, it was using like 20W power to fly a few grams11:36
wpwraki wouldn't have expected it to be able to even lift itself :)11:36
wpwrakwell, add a H2O2-based first stage plus a solar panel and you're ready to conquer the stars ;-)11:37
wpwrakhmm, about 3 minutes total etching time. still not bad at all.12:22
qi-bot[commit] David Kühling: undo hosts file fix.  Xiangfu was quicker and did it better :) http://qi-hw.com/p/openwrt-xburst/2792c8b14:42
kristianpaul(well, add a H2O2-based first stage plus a solar panel and you're ready to conquer the stars ;-) )  Yes !!15:16
kristianpaulwejp: actually for lunar goolgle price i'm have good feelins with this team https://www.arcaspace.com/15:17
kristianpaulahh you're talking a about rocket based first stage?15:18
kristianpaulH202 >> rockoon15:21
kristianpaulwejp: sorry i meant wpwrak15:22
wejpheh, no problem ;)15:22
wpwrak(h2o2 -> rocket) yes16:25
wpwrak(arcaspace) oh, with a balloon to the moon ? tres jules verne ;-)16:26
qwebirc61468alguien habla español17:23
kristianpaulqwebirc61468: hola17:24
qwebirc61468de donde es?17:24
qwebirc61468de chile amigo :)17:24
kristianpaulBievenido :)17:25
kristianpaulqwebirc61468: tienes un nanonote?17:25
qwebirc61468quiero tener el nanonote por eso ingrese aqui17:25
qwebirc61468como cambio el  nombre17:25
qwebirc61468se usa algun comando17:25
kristianpaul /nick nombre17:25
qwebirc61468lo supuse17:26
kristianpaulsi el espacio incial :)17:26
kristianpaulok :)17:26
seplvedaahi si17:26
seplvedaque edad tienen?17:26
kristianpaulla justa para escribir en irc ;-))17:26
seplvedaen la empresa17:26
seplvedao son usuarios ?17:27
Action: kristianpaul usuario17:27
seplvedaaah ok17:27
seplvedapensé que eran ejecutivos17:27
kristianpaulcreo  andres-calderon si :)17:27
seplvedanecesito importar este producto17:28
kristianpaultiene tarjeta credito?17:28
seplvedaaqui a chile no llega y venderlo seria el boom17:28
seplvedaobviamente se puede comprar por internet17:28
seplvedapero no quiero 117:28
kristianpaul10000? :D17:29
seplvedalo chilenos somos soñadores17:29
kristianpaul10 es una buena forma de empezar seplveda17:29
kristianpaulya veo .)17:29
seplvedaigual me gustaria utilizar el producto17:29
kristianpaulhttps://sharism.cc/shop/contact_us.php <-- si quieres mas info comercial17:30
kristianpaulsharism es el fabricante de los nanonotes17:30
seplvedacomo ve paree que es chino17:30
seplvedaque tal el producto kristianpaul17:31
Action: kristianpaul <3 su nanonote17:31
seplvedaposees otro notebook ?17:32
seplvedaque no puedes hacer en él ?17:32
kristianpaulnotebook si, que no puedo hacer... buena pregunta17:33
kristianpaulyo solo queria esuchar musica y un dicionario, y pegarle mi gps lo de mas fue bievenido :)17:33
seplvedayo en cambio necesito programa en distintos lenguajes  y utilizar softwares matematicos17:35
seplvedacrees que soporte ese uso?17:35
kristianpaultu pregunta es muy amplia17:36
kristianpaullastimosamente no he usado sofware matematico,17:36
kristianpaulse de otros proyectos usando fftw17:36
kristianpaullenguages puedes usar C, lua, python..17:37
kristianpaulel nanonote actualmente cuenta con sofware de openart y jlime(open emdebbed) alli puedes tener mas info de que esofware esta disponible con detalle17:37
seplvedaclaro, por programas matematicos wolfram17:38
seplveda<3 phyton17:38
zrafa some docs coming : http://en.qi-hardware.com/wiki/Jlime17:44
kristianpaulzrafa: thos can be re-used with the last oe (muffiman) ?17:45
zrafakristianpaul: nope. I think that I already said which is the difference of jlime at qi.. and jlime :)17:46
kristianpaulyes yes17:46
kristianpaul(bad memory)17:46
Last message repeated 1 time(s).17:46
kristianpauloh yes thats bad17:46
zrafajlime uses OE and :)17:47
zrafakristianpaul: hey.. how is the life ?17:47
kristianpaulzrafa: good :)17:47
zrafavery well as well17:48
kristianpaulzrafa: this jlime you pointed, are you plannin to document how was built?17:50
kristianpaulI saw same docs for free of patent owrt used in nanonote as well :)17:50
wpwrak(jlime docs) great !!17:53
zrafakristianpaul: how was built: nah... that is old I would say.. and I think that users do not want to build the same stuff which is already built :P.. But let me give you a chance.. I know you like how qi works with development.. and you have asked me several times about how to built the same muffinman version already built. So If you really needs that I can write.. WARNING: I will write the current OE docs explaining which exact commit I used from OE git a17:54
zrafahow I added the extra applications17:54
kristianpaulzrafa: well i know how build muffiman, you help on that, i just was talking about documentation in qi wiki :)17:55
zrafakristianpaul: ah.. did I? :P.. I am old and forget17:55
kristianpauli hope OE have good layers ;)17:55
kristianpaulzrafa: yes you did17:55
zrafakristianpaul: well, I do not have a lot of free time to write that :(17:55
zrafaI would prefer to write the stuff users still needs17:56
kristianpauli'm afraik as that is missing the image will get old as time pass..17:56
kristianpauli understand and end user is very important :)17:56
zrafakristianpaul: what is old? :)17:56
kristianpauljust ignore me :p17:56
zrafakristianpaul: I do not think that it will get old17:56
kristianpaulzrafa: why?17:56
zrafakristianpaul: two things:17:57
wpwrakzrafa: if there's a specific timestamp, revision, or such, that identifies the upstream revision, that may be useful to mention. (but i doubt there a single identifier, or is there ?)17:57
kristianpaulwpwrak: is some webpage i cant mention because i dont have a layer ;-)17:57
kristianpauls/is/it is17:57
wpwraklayer ?17:57
kristianpaulsome text files, very usefull :)17:58
wpwrakah :_17:58
kristianpaulmy fauly english sorry :)17:58
zrafakristianpaul: 1- what does old mean?.. if you mean "packages" will get old and newer versions will come then it will get old completely. You will need to build a new repository completely. But I think that a sane and good repositoy like jlime has would be useful for a couple of years.. ANd 2-17:58
zrafakristianpaul: 2- This jlime version for qi also brings a bootstrap version,17:58
kristianpauloh bootstrap sounds good17:59
zrafayou can use for building your own version from scratch (if you mean about old like you would like to see another GUI or way)17:59
zrafayou just take bootstrap and install on that the packages you want to have the GUI you want, etc17:59
wpwrakzrafa: (couple of years) hmm, probably not. we have to make sure things are easy to keep up to date. basically automate what you did manually. qpkg tries to go in that direction - i just have to finish it ;-)17:59
kristianpaulwpwrak: (qpkg) great !18:00
kristianpauli really want to move OE based free of patent distro fr my nanonote, but i'm afraid automate building for long term18:00
zrafawpwrak: I think that we are talking about many things.. What is exactly "getting old"?.. all gets old..18:01
kristianpaulzrafa: okay lets replace get old to follow upstream :)18:02
zrafakristianpaul: well, I am not going to work with OE and free of patents stuff.. no time for that. In fact, I already said that I am not the best fan of OE.. so if I do something.. I will try to have a repository of packages.. just that. I will not use OE to build rootfs, or similar kind of weird things. I like OE for the repo it builds18:03
kristianpaulzrafa: (best fan of OE) ohh wow i you're, i missed that backlog :)18:04
zrafakristianpaul: follow upstream is really hard. Jlime is not working with "free of patents" versions18:04
kristianpauls/i/i tought*18:04
zrafakristianpaul: nah.. I worked with OE because I like how easy you can build a nice repository for embedded devices. No more18:05
zrafakristianpaul: and I used it because JLime uses it.. if jlime devs likes Conectiva Linux I will use (still if it is dead) :D18:05
zrafawpwrak: I would like to have the few tools around jlime really useful for all (like qpkg, or the theora player, or the wikireader, etc).. But that is different with maintain documentation for development/OE built repositories/rootfs OE building documentation up to date18:08
wpwrakzrafa: (get old) i mean that things need updating from time to time. so it's best to have a process that makes this painless.18:08
kristianpaulzrafa: wikireader :) sure go ahead !18:09
wpwrakzrafa: my idea is that you could just flag problem packages as undesirable and then qpkg could tell you which packages can no longer be installed. or it could generate a list of packages that can, depending on what you're after.18:10
zrafawpwrak: yes, you are right.. BUt we need to convice more people to help :).. Currently JLime has around 7, 8 devs.. for 4 or 5 platforms/devices.. Just me was trying to have something to use on qi/resellers.. SO when I work on that, jlime lose onde dev, because other devs are not trying to work with this kind of stuff18:11
wpwrakzrafa: or maybe add some dependencies into upstream (OE or "full jlime", whichever works best) and tell qpkg to knock out some dependency and generate the resulting list of available packages.18:11
zrafawpwrak: wait...18:12
wpwrakzrafa: you need to do a bit more propaganda :-) the problem is not unique to qi-hw.18:12
zrafawpwrak: how would qpkg relate with OE full jlime?.. It was clear that versions for qi/resellers should not include links to complete repositories, still if tha package manager will not install problematic packages.18:13
wpwrakzrafa: my idea is that you basically take some upstream package set, add your extra wishes, and let qpkg produce a subset of the upstream18:14
zrafaah.. nice.. I see now18:15
wpwrakzrafa: the subset would be self-contained, like the one you've produced manually so far18:15
wpwrakzrafa: the form in which those extra wishes would appear is open to debate. once the infrastructure for resolving dependencies is there, it's relatively easy to do other things with it.18:16
wpwrakzrafa: qpkg can already solve many installation dependencies. what it doesn't do yet is handle cases where you need some complicated backtracking and it doesn't sort its output by dependency18:17
wpwrak(both need the same underlying algorithm - alas not an easy one. will take me a few days to figure out)18:18
wpwrakzrafa: this regression test illustrates the problem qpkg can't handle yet: http://projects.qi-hardware.com/index.php/p/wernermisc/source/tree/master/qpkg/test/bug-adding18:21
wpwrakzrafa: it basically marks packages a being about to be installed, but then finds out that it can't do this, and when trying some alternative, it doesn't take into account that the packages it considered for installation weren't18:22
wpwrakzrafa: not sure if this is constellation is very likely in real life, but it's something that can be expressed, so i better handle it18:23
zrafawpwrak: I need a while to understann all you wrote :)18:24
wpwrakit's a little bit complicated :)18:28
wpwraklunch time :)18:58
zrafahaha :D18:58
kristianpaulzrafa: what do you use your nanonote for?19:19
kristianpaulBtw i wonder if decemenber in argentina is as noissy as in here :S19:19
zrafakristianpaul: no much use these days.. I like it to play music files, wikireader when traveling.. and games19:24
wpwrakkristianpaul: you mean december in general ? :)19:25
kristianpaulwpwrak: yes19:27
wpwraknaw, pretty normal. except for the 24th and a few small test runs before and after19:28
kristianpauldamn my neighboors noise is goint to kill me19:28
kristianpaulhe "small test runs"19:28
zrafakristianpaul: your neighboors do many parites?19:29
wpwrak(we have fireworks on the 24th. military grade :)19:30
kristianpaulparties are 24 and 31 i guess19:30
zrafakristianpaul: which kind of noise?19:30
wpwrakin fact, i'll get some armament tomorrow :)19:30
kristianpaulhihg volume music (bad electronic, and musica de cantina, repetida ;))19:30
kristianpaulreggueton :S also19:31
wpwrakso strike back. which movie was that .. apocalypse now ? where they played wagner from the helicopters19:32
kristianpaulno idea, i'm not good with holliwood-like movies :-)19:32
zrafakristianpaul: wpwrak : when I was working few days in Caracas.. my company rented an apartment.. well all the nights the neighbors houses were doing parties listening reggeton music and laugh all the time the whole night19:33
zrafawell all=well, all19:33
zrafakristianpaul: so that sounds similar like you are suffering there :)19:34
kristianpaulcaracas .ve ?19:34
kristianpauloh yes they are party makers before born :)19:35
zrafawpwrak: do you remember how we installed toolchain and set the proper links for reporitories? :) .. I need the doc of that for the last link here : http://en.qi-hardware.com/wiki/Jlime19:36
zrafa"Jlime Toolchain Documentation"19:36
wpwraki really ought to visit .ve some day ;-)19:36
kristianpaulah travel is so relaxing :)19:38
kristianpaulbrb i'll try Fedora and milkymist devel env on it19:39
wpwrakzrafa: (repo link) hmm, i think you had some file for me to download19:39
wpwrakzrafa: i think my notes are on the dead disk. but the discussion ought to be in the irc log19:39
wpwrak(*somewhere* in there :)19:40
zrafawpwrak: we can put that link at "Jlime Toolchain Documentation" wiki page ;-)))19:43
zrafasomething like "all is explained at http://en.qi-hardware.com/irclogs/index.html"19:43
wolfspraulandres-calderon: hi good morning!20:04
wolfspraulI started to cleanup the xue file a little, here's my rough plan now...20:15
wolfspraulsee what werner thinks about renaming kicad/library to kicad/components20:16
wolfspraulwe are using 'components' in other kicad projects, maybe that's a good name to standardize on, and the rename should be safe20:16
wolfspraulthen, create a new directory kicad/camera, and move the camera and camera_psu sheets there, removing them from kicad/xue-rnc20:17
wolfspraulautomate the creation of the module files from fped files in kicad/modules20:17
andres-calderonwolfspraul: Hi20:17
wolfspraulhi, good to see you!20:18
wolfspraulI'm starting a little cleanup, lots more to come. please give me feedback if something is wrong.20:18
andres-calderonwolfspraul, the standardization is good.20:19
wolfspraulandres-calderon: are you OK with those things I am listing?20:19
wolfspraulalso create new kicad/camera directory, move camera there (daughterboard), etc.20:19
wolfspraulwell we have tons more. if you can join please do so.20:19
wolfspraulI will favor speed over accuracy now.20:20
wolfspraulso I may introduce new bugs20:20
wolfspraulbut if we don't speed up, the project will never be manufactured20:20
wolfspraulandres-calderon: also I noticed there where little scripts 'clean' committed.20:20
wolfspraulI will delete them, and add proper .gitignore files.20:21
wolfspraulthere is a file docs/xue-bom.ods (I renamed it from a much longer name)20:21
wolfspraulI think I want to delete it, it only has a few URLs for memory chips, and even those are just web pages not pdfs20:21
wolfspraulwhen I'm done with all these things, I will probably start looking into the schematics ERC errors20:22
andres-calderonI'm  selecting  the BOM of the Xué's PSU (again..),  This time based on DigiKey availability20:22
wolfspraulah, before that I will remove the AVR, FAN and ft223220:22
wolfspraulandres-calderon: is it ok that I delete docs/xue-bom.ods ?20:22
wolfspraulthen I will slowly start with boomification, first with an empty bom/ directory and a little Makefile structure, filling in more later20:23
wolfspraulin sim/verilog/micron, we have 2 .zip files committed20:24
wolfspraulmaybe as a first step I will unpack them and commit what's inside instead20:24
andres-calderonTomorrow I will fix the ERC errors and warnings.20:24
wpwrakyes ! 2nd try works much better :)20:24
wolfspraulandres-calderon: do you see anything wrong with what I've posted?20:25
andres-calderonwpwrak: I will be more conservative.20:25
wolfspraulI am currently working in a mode of "when I don't hear anything, that means silent approval"20:25
andres-calderonwolfspraul: not yet.20:25
wpwrakwolfspraul: (library -> components) it would be consistent with my use, but i don't have a strong opinion on it. kicad terminology may change a little anyway, as these things get rearranged.20:26
wolfspraulyes I know, but let's go for consistency at least right now20:26
wolfspraul(good action on KiCad btw, nice to see the progress there...)20:26
andres-calderonwolfspraul: From now I am full time in the Xué project.20:27
wolfspraul(distributed library management system...)20:27
wolfspraulandres-calderon: what about those 2 zip files?20:27
wolfspraulI will first unpack them, peel the onion as werner says20:27
wpwrakandres-calderon: (2nd try) ah, that was about my little ben-wpan board ;-) yesterday, i had a very frustrating day with a board that doesn't work for some obscure reason. today i made a new one and it seems to work.20:28
wolfspraulandres-calderon: also, in the root xue/ directory there is now a Makefile that will make some things easier20:28
wolfspraulyou can do 'make sch' or 'make brd'20:28
wolfspraulI will add more20:28
andres-calderonAre micron files (IBIS files), used in to automatic kicad component generation20:30
andres-calderonIBIS files can be read by the  ibis2kc.py script (http://projects.qi-hardware.com/index.php/p/xue/source/tree/master/emqbit-utilities/kicad/ibis2kc.py)20:34
wolfspraulandres-calderon: my removal of avr, fan, 2232, camera, camera_psu may well create more bugs/ERC errors in the schematics20:34
wolfspraulbut I will first remove and move things, then look at the details.20:34
wolfsprauljust explaining my approach. before you do anything, don't forget 'git pull' :-)20:35
wolfspraulwpwrak: for directory name, once we commit dxf files for mechanical/case work, what would you call the subfolder?20:36
wolfspraulcase? mechanical? both not very good20:36
wpwraki call them "cam", but this may be a bit confusing in this context :)20:38
andres-calderonmay be "case" directory  into  a "mechanical" directory20:39
qi-bot[commit] Wolfgang Spraul: unzipped 2 files http://qi-hw.com/p/xue/29e7ced20:39
wolfsprauland what does 'cam' stand for? I'm not sure I like it even outside of xue...20:39
wpwrakwolfspraul: andres mentioned that he wanted the FANxxx for optimizing the fpga's (usually very high) power consumption20:39
wpwrakComputer Aided Manufacturing. basically CNC and stuff.20:40
wolfspraulandres-calderon: let's make xue as simple as possible. have you used FANxxx before for this purpose?20:42
wpwrakfor example, see http://projects.qi-hardware.com/index.php/p/ben-wpan/source/tree/master/atusb/cam2/mkmk20:42
wolfspraulI would strongly argue for removing them, not on technical facts but looking at our manpower, risk that it won't work or backfire, manufacturing complexity, etc.20:43
wpwrak(this uses the tools i developed in the last days, to let me automate more of the pcb making)20:43
andres-calderonwpwrak, wolfspraul:  I've been converted. I think that simplicity is the name of the game.20:43
wpwrakhehe ;-)20:43
wpwrakandres-calderon: maybe keep the series/sense resistor but make them 0R. that way, you can remove them and insert a current meter/probe in the lab.20:44
qi-bot[commit] Wolfgang Spraul: removed xue-bom.ods which only had a few web links for memory chips http://qi-hw.com/p/xue/c0089b720:45
andres-calderonI will discard the  onboard measurement of energy. Maybe add  a set of test points (plus 0 ohms resistors)20:46
qi-bot[commit] Wolfgang Spraul: renamed kicad/library to kicad/components for consistency http://qi-hw.com/p/xue/99067ec20:47
wolfspraullet's see whether schhist survives that20:47
wolfspraulwe have a few empty .dcm files in kicad/components, unless there is a reason against it I would propose to delete them20:48
wolfspraulandres-calderon: from 12 .fpd files in kicad/modules, 11 are machine generated20:50
wolfspraulwhat is the plan with that now? where will future edits be made?20:50
andres-calderonwolfspraul: I'll make a makefile20:51
wolfspraulto create the .fpd ?20:51
wolfspraulor to go from .fpd to .mod?20:51
wolfspraulwe have 22 empty .mdc in kicad/modules, if it's safe to delete them I will probably delete them20:52
wolfspraul(I'll wait until Werner is back he knows KiCad best...)20:52
andres-calderonI will review the makefiles of the GTA02 core project20:55
wolfspraulthat's quite old by now, I suggest ben-wpan20:55
andres-calderonwolfspraul, ok20:55
wolfspraulandres-calderon: how were the .fpd generated?20:58
wolfspraulwas it a one-time concversion, and future edits will be made in .fpd, or will the source stay the source for edits20:59
wolfspraulright now they say "don't edit"20:59
wolfspraulah no, they don't say that :-)20:59
wolfspraulbut they say "MACHINE GENERATED"20:59
andres-calderonwith the FPED editor20:59
wolfspraulthey were created with the fped editor?21:00
wolfspraulI'm wondering about the 'MACHINE GENERATED' comment21:00
kristianpaulHello i'm back now from Fedora (MIlkymist dev mainlly reason) :)21:02
kristianpaulLets see how it goes21:02
wolfspraulFedora has SELinux enabled by default, right?21:04
kristianpauldont know21:04
wolfspraulnever worked with that before, had to get used to a few bumps21:04
kristianpaulah yes i got some auto-bugs pop ups from SELinux..21:05
wolfspraulyeah. first time for me, I was always happy that it passed me, but now I guess it's time :-)21:06
wolfspraulwpwrak: there you are :-)21:10
wpwraktroublesome connection21:10
kristianpaulhmm this is because xilinx installer, tricky21:10
wolfspraulhow do you feel about deleting empty .dcm and .mdc files?21:10
wolfspraulwhen fped creates a .mod file out of a .fpd file, does it also create the .mdc file?21:11
qi-bot[commit] Andres Calderon: kicad modules makefile has been added http://qi-hw.com/p/xue/c49a03721:12
qi-bot[commit] Andres Calderon: Merge branch 'master' of projects.qi-hardware.com:xue http://qi-hw.com/p/xue/be6e03b21:12
wpwrakno, it doesn't generate the.mdc file. so you'll get a complaint from cvpcb21:14
Action: kristianpaul setenforce 0 21:15
wolfspraulif there are complaints, that means we should leave empty .mdc and .dcm files?21:28
wolfspraulmaybe the .dcm can be deleted?21:28
wpwraka marketing question: should atusb have a full-sized USB connector, like here http://downloads.qi-hardware.com/people/werner/tmp/nemesis.jpg21:28
wpwrakor mini-USB, like here http://www.almesberger.net/misc/ben/wpan/board-100813.jpg21:29
wolfspraulthe alternative would probably be micro-usb right away, and those platforms are normally so closed that it will be very hard to get atusb to work21:30
wpwrak(the general shape would be that of the first one)21:30
wpwrakno micro-usb :)21:30
wolfspraulthere are very few devices that have a mini-usb host receptor21:30
wolfspraullike the Neo FreeRunner :-)21:30
wpwrakmicro-usb is for idbg. let's not confuse things ;-)21:30
wolfspraulI am thinking from the other side - what to plug it into...21:31
wolfspraulfor the full-size, it will be notebooks, netbooks, maybe open tablets21:31
wpwrakit's basicallly either pc directly or via cable21:31
wolfspraulfor mini-usb, I doubt many devices exist at all21:31
wpwrakwith cable21:31
wolfspraulfor micro-usb, a lot of devices exist with usb-on-the-go, but they will be too closed to have fun with atusb21:32
wolfspraulsure cable is another option21:32
wpwrakpro: can find better placement. contra: if you can't get rid of the cable21:32
wpwrakthere are also full-sized USB cables, but they're not so easy to find21:32
andres-calderonwolfspraul:  I already deleted the mod. files (and has been a makefile based in the ben-wpan modules makefile)21:32
wpwrak(digi-key has them, though ;-)21:33
wolfspraulandres-calderon: I saw it, great21:33
wolfspraulwhen you committed, did you see the merge commit?21:34
wolfspraulthere is a way to avoid that, I think before you push your commits, you do a 'git fetch origin' and then 'git rebase origin/master'21:35
andres-calderonwolfspraul: I dont know anything about the  mdc files. They are used when the module is added to the design...21:36
wolfspraulsure don't worry those are tiny details21:36
andres-calderonwolfspraul: just, pull -> add  -> commit -> push21:37
wolfspraulwpwrak: I'm ok with 'cam' right now for mechanical stuff21:38
wolfspraulI don't need it urgently anyway, but it's a good first step21:38
wpwrakso .. full-size usb A plug or mini-usb B receptacle ? :)21:39
kristianpaulwpwrak: full-size i think21:40
kristianpaulstill more universal for usb adapters21:40
wpwrakany other votes ?21:40
wpwrakseems that we have an unanimous vote :)21:44
wpwraknow i have to figure out why my full-sized usb resets all the time ...21:44
kristianpaulnot reset in mini-usb?21:45
wpwrakthe design i made in august, with mini-usb has no usb problems. (the rf side is a disaster, though)21:46
wpwrakthe new one, with full-sized USB, has big troubles staying up. not sure why - the usb circuit is basically the same as in "cntr" and very similar to the old atusb, idbg, etc.21:47
wpwrakso there's still a bit of a mystery21:47
qi-bot[commit] Wolfgang Spraul: deleted empty .dcm files http://qi-hw.com/p/xue/a3b6d3621:50
wpwrakanyway, time for me to go to bed. have to get up early tomorrow.21:55
kristianpaulhave good sleep21:55
Action: kristianpaul getting fun setting up fedora21:56
wpwrakthanks ! have fun ! ;-)21:56
kristianpaul:P https://fedoraproject.org/wiki/PackageKit_Items_Not_Found#Missing_Codec22:22
kristianpaulhey fedora fits very well to our free-of-patent world :)22:24
--- Sun Dec 19 201000:00

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