#qi-hardware IRC log for Sunday, 2010-10-17

qwebirc35353wpwrak: Hey, This what I got when I booted my 16GB sd card, with first partition 2GB ext2 type:  File not found /boot/uImage   Wrong Image Format for bootm command   Error: can't get kernel image!00:01
wpwrakhmm, rafa ?00:02
wpwrakqwebirc35353: i haven't played with booting from uSD on the ben yet, so this message doesn't ring any bells00:02
qwebirc35353wpwrak: gotcha00:03
qwebirc35353rafa: you still there00:04
wolfspraulqwebirc35353: hmm, so if that is the same bug like the u-boot ext2 filesystem bug I have in mind, then it means it may be related to a large block size or something else that is large on the 16gb card, irrespective of the partition size.00:06
qi-bot[commit] Werner Almesberger: boom/dist/dk/dk-catq.pl: allow out-of-stock parts http://qi-hw.com/p/eda-tools/b66b71f00:07
qi-bot[commit] Werner Almesberger: manu/Makefile were highly redundant. Moved their content to a common Makefile. http://qi-hw.com/p/eda-tools/ac7ebdd00:07
wolfspraulwe are on this bug, but I cannot promise it's fixed in a day or so. Let's see when xiangfu is back what he has found out about it lately.00:07
wpwrak12629 parts now00:07
qwebirc35353wolfspraul: ok, then I will try my 4 GB sd card then00:07
qwebirc35353thanks00:07
qi-bot[commit] Werner Almesberger: Oops, murata-grm.catq wasn't committed http://qi-hw.com/p/eda-tools/afda18a02:12
qi-bot[commit] Werner Almesberger: Makefile (CHR): generate from list of manufacturer names http://qi-hw.com/p/eda-tools/db2ecbf02:12
qi-bot[commit] Werner Almesberger: Added TDK C series of ceramic SMT capacitors. http://qi-hw.com/p/eda-tools/fd67bc902:12
qi-bot[commit] Erwin Lopez: initial import http://qi-hw.com/p/sie-ceimtun/0a65a5002:51
kyakhmm.. i wonder why process '/bin/sh /etc/init.d/rcS S boot' never exits03:42
kyakit just sit there all the time, eating 1.3M of memory03:42
wolfspraulhmm. in OpenWrt?03:49
kyakwolfspraul: yes03:59
kyakdo you see it?03:59
wolfspraulI ran some nand testing no rootfs right now :-)04:00
wolfspraulbut if that process is really there and has nothing to do, seems like we can recover 1.3M :-)04:01
kyakindeed we can04:01
kyakwhen i compare with openwrt on linksys router, this process exits04:03
kyakmight be that one of the initialisation scripts is not exiting correctly04:03
kyakalso, i would get rid of logger and klogd (thus freeing another 2.6 Mb of memory)04:06
kyakthey are useless most of the time and can be activated on demand, when one needs to debug something04:07
kyakxiangfu: hi05:03
kyakxiangfu: i think there is a problem with fnkeys05:04
kyakit has no facility to daemonize, therefore it is started as 'fnkeys $DEVICE_PW &' from /etc/init.d/fn-handle05:05
kyakbut this way, /etc/init.d/fn-handle wait forever for fnkeys to exit05:05
kyakthus, '/bin/sh /etc/init.d/rcS S boot' and 'logger -s -p 6 -t sysinit' are also hanging there forever05:06
kyaklogger is blocked in read()05:06
kyakin total, there are two additional processes that should not be there after the system is booted: '/bin/sh /etc/init.d/rcS S boot' and 'logger -s -p 6 -t sysinit'05:07
kyakxiangfu: the way around it is to start fnkeys this way: start-stop-daemon -S -x /usr/bin/fnkeys -b $DEVICE_PW05:20
xiangfu_kyak: Hi. thanks for report.05:45
xiangfu_kyak: let me boot my nanonote. test it again. :)05:47
kyakxiangfu_: sure05:47
kyakbtw, i also got rid of unused tty's, syslogd and klogd - not it;s using less then 13 Mb after boot05:52
kyak*now it's05:52
kyakthis is with mmc, ubifs:data mounted and one login session via ssh05:53
xiangfu_so you think the  syslogd and klogd is useless for NanoNote. do you think we should disable them by default ?06:00
kyaki decided to disable it for myself, i'm not sure it is better for everyone06:02
xiangfu_kyak: ok. let's just keep them there by default. in fact I never check my pc logs.  :)06:03
kyaki check them on my PC only when i have some problems and need to debug something06:05
xiangfu_wolfspraul: Hi, uploaded : http://en.qi-hardware.com/wiki/File:Openwrt-screenshot-2010-09-14.png06:05
kyakxiangfu_: if you don't mind, i can commit the modified fn-handle/files/fn-handle.init06:06
xiangfu_kyak: go ahead.  thanks for your commit.06:07
qi-bot[commit] kyak: fnkeys is now correctly daemonized at start http://qi-hw.com/p/openwrt-packages/1a6e2dc06:08
kyakxiangfu_: np06:08
kyakxiangfu_: http://downloads.qi-hardware.com/people/kyak/tmp/file.png06:25
kyaka cooler screenshot, with sdcard free space shown :)06:26
xiangfu_kyak: cool06:27
xiangfu_kyak: Hi. after apply your patch. there are still in two "/bin/sh /etc/init.d/rcS S boot" one "logger -s -p 6 -t sysinit" here.06:28
kyakhm, that's strange06:31
kyakdo you have gmenu2x started by default?06:32
xiangfu_kyak: yes. here is the "ps aux" : http://pastebin.ca/196473406:34
kyaki don't have it, but if you do, and it's started from /etc/init.d/start, then it causing the same thing as fnkeys06:34
kyak/bin/sh /etc/rc.common /etc/rc.d/S99start boot06:35
kyakthis one also never exits06:35
xiangfu_kyak: I am asking this question in #openwrt. hope someone can help me to debug.06:47
kyakit's not really openwrt-related.. i'm trying the same trick with start-stop-daemon now/...06:48
wolfspraulkyak: wow so you freed at least 1.3 MB for everybody!06:55
wolfspraulwell everybody using OpenWrt06:55
kyakwolfspraul: not yet :) gmenu2x is still preventing it06:58
wolfspraulxiangfu_: thanks for the screenshot, embedded in news...07:00
xiangfu_kyak: yes. ask for some tips. they suggest me use "start-stop-daemon -S -b -x /usr/bin/gmenu2x"07:00
xiangfu_kyak: just like you have done in fnkeys.07:01
kyakxiangfu_: it would work, but gmenu2x requires some variables set from /etc/profile07:03
kyakotherwise it won't start07:05
kyaki started it with a wrapper now start-stop-daemon -S -x /usr/bin/gmenu2x.sh -b07:06
kyakwhere i source the /etc/profile07:06
kyakbut now there are three processes: /bin/sh /usr/bin/gmenu2x.sh, /bin/sh /usr/bin/gmenu2x, ./gmenu2x07:07
kyakothers that we bothering me are gone07:08
xiangfu_kyak: I just tested. "start-stop-daemon..." doesn't start the gmenu2x.  I think we just add "&" to the end of gmenu2x.07:08
kyakbut three processes to start one app - too mcuh :)07:08
kyakxiangfu_: it won't start it because of lack of SDL_NOMOUSE and other vars07:09
qi-bot[commit] Xiangfu Liu: update config.xbboot comments http://qi-hw.com/p/openwrt-xburst/d52f29607:10
qi-bot[commit] Xiangfu Liu: make gmen2x run in background http://qi-hw.com/p/openwrt-xburst/6cdcc4007:10
xiangfu_kyak: now the "/bin/sh /etc/rc.common /etc/rc.d/S99start boot" exit after run gmenu2x.07:10
xiangfu_kyak: dinner time, back later.07:12
kyakbon appetit07:12
kyakxiangfu_: with the "&", the /bin/sh /etc/init.d/rcS S boot and logger are still there...07:13
kyakthis only makes the gmenu2x detach from terminal, but doesn't really allow the parent terminal to exit07:13
kyakand so it waits... eating precious memory07:14
wpwrakit may help to always have a bit of swap enabled. just to get rid of hardly ever used pages. (of course, avoiding to have them in the first place is even better)07:19
wpwrakis it possible to swap to ubifs ?07:20
kyakwhy not?07:22
kyaki have a swap on sd card07:22
kyakbut i'd still like to fight for free RAM07:22
wpwrak(sawp on ubifs) sometimes, when the system tries to evict pages in a memory shortage, complex subsystems can't be used to write the data, because they need to allocate significant amounts of memory on their own to do their work. swap over nfs comes to mind.07:42
wpwrakubifs certainly qualifies as "complex". but i don't know how bad it is with memory. e.g., if it figures it needs to migrate the block it's trying to swap to, what happens ?07:43
wpwrak(fight for free RAM) definitely a good idea. i'm just saying that having a bit of swap around can ease memory pressure even more.07:44
kyakxiangfu_: i use this line "SDL_NOMOUSE=1 start-stop-daemon -S -x /usr/bin/gmenu2x -b" (no need for source /etc/profile) and edit /usr/bin/gmenu2x to have "#!/bin/sh" as first line07:55
kyakxiangfu_: now there are only two processes related to gmenu2x and others are exited07:57
kyaknow a good idea would be to get rid of that wrapper /usr/bin/gmenu2x at all08:02
xiangfu_kyak: go ahead.08:02
wolfspraulwpwrak: just reading about EDIF http://en.wikipedia.org/wiki/EDIF08:24
wolfspraulthat sounds depressing...08:24
kyakxiangfu_: looks like this is the best what we can do.. gmenu2x won't start as daemon08:28
kyakso two processes is the least08:28
kyakxiangfu_: if you have access to gmenu2x git, you can update gmenu2x.sh file there (it is copied to /usr/bin/gmenu2x)08:29
kyakand check if that SDL_NOMOUSE=1 start-stop-daemon -S -x /usr/bin/gmenu2x -b works for you...08:29
qi-bot[commit] Xiangfu Liu: update the gmenu2x.sh, add shell script head http://qi-hw.com/p/gmenu2x/9986a1f08:47
qi-bot[commit] Xiangfu Liu: use start-stop-daemon to start gmenu2x, thanks to kyak http://qi-hw.com/p/openwrt-xburst/4c5ae5d08:49
xiangfukyak: ^  committed.08:49
Action: xiangfu found the gmenu2x input configure is changed.08:49
kyakxiangfu: thanks!08:51
kyakxiangfu: btw, no need to source /etc/profile now..08:52
xiangfukyak: oh. yes. I forget. really sorry.08:55
qi-bot[commit] Xiangfu Liu: use start-stop-daemon to start gmenu2x, thanks to kyak http://qi-hw.com/p/openwrt-xburst/ad57f3608:55
xiangfukyak: since no one commit to openwrt-xburst. and no now have run 'git pull', I will rebase those three commit :)08:56
kyakxiangfu: yeah, use the git at full :)09:00
Action: xiangfu delete the branch [tracking_trunk], since it's same with upstream.09:01
qi-bot[commit] Andres Calderon: header25x2_smd_2mm footprint added http://qi-hw.com/p/xue/44ffe7809:27
wolfspraulwpwrak: reading through boom... just something to think about: for inventory, it might be a good idea to keep lots of the exact same components, acquired from different sources, separately09:41
wpwrakwolfspraul: (edif) kinda like the fragmented Unix world before POSIX gave them a standard and Linux increased the pressure enormously09:41
wolfspraulthis may not be part of the boom/shopping list problem, but I still wanted to mention it09:42
wolfspraulsometimes there is also something like -ES (engineering sample) where the vendor says:09:42
wolfspraula) this component can only be acquired in low quantities as -es09:43
wpwrakwolfspraul: yes, mean same = same manufacturer but different distributor ?09:43
wolfspraulb) there may still be bugs, or maybe not, no guarantees09:43
wpwrakerr .. s/yes,/you/09:43
wpwrak(was about to write something different, then changed course in mid-sentence :)09:43
wolfspraulyes different place you bought from09:44
wolfspraulif it's the same part from the same source, maybe it can always be lumped together? I haven't seen a reason yet where it would need to stay separate.09:44
wolfspraulsome parts have requirements like "use within x days" though.09:44
wpwrak-es could just be a different part number. then you can say (or not) that foo equals foo-es well09:44
wolfspraulsure sure, your system is very flexible since it's spread out like a relational database09:45
wolfspraulI just wanted to write what went through my mind.09:45
wolfspraulso sometimes you have a sealed bag, and after opening you need to use the parts within 5 days09:45
wolfspraulprobably no need to factor this in, but it can affect planning, sometimes09:45
wolfspraulsometimes you can re-seal the unused ones, but sometimes not, depends on your equipment too09:46
wpwrak(equalities) i don't have one-way equalities, though. e.g., some part that has the same footprint but a different package size. you could use the smaller package in a design for the larger but not vice versa09:46
wolfspraulthen you sometimes have date codes, which you may or may not want to track or factor in09:47
wpwrak(best-before date) yes, that's something a factory inventory needs. not sure if this really ought to be part of boom, though09:47
wolfspraulagree09:47
wolfspraulwe need to focus09:47
wpwrak(factory inv) e.g., the factory could simply generate an inventory with parts effectively available09:48
wolfspraulI want this thing to be able to serve as our shopping tool for our handful of designs asap09:48
wpwrak(track) i think the factory basically wants to track every item. when ordered, when arrived, who checked it, where was it stored, when was it taken out and by whom, how much was used, when did it go back, etc.09:49
wolfspraulso with datecodes, if you have older datecodes and newer datecodes, you may either first take the older ones (if it's your own inventory), or you may take the newer ones (if you are comparing two distributors you are buying from)09:49
wolfspraulwell it depends09:49
wolfspraulthere needs to be a business reason09:49
wpwrakfor exmaple, you may get bad lots09:50
wolfsprauland things need to be re-evaluated too, no need to continue with some system that has long lost any connection to reality09:50
wpwrak"discard all cpus delivered from source X between dates Y and Z"09:50
wolfspraulthen I read about the KiCad workflow a little more09:50
wolfspraulremember a while back we tried to identify original vs. generated files09:50
wolfspraulback then you said the netlist is generated, but you weren't entirely09:51
wolfspraulsure09:51
wpwrakyou may also have processes that accidently damage parts. also, if you check things in and out, you have a semi-automatic record. better than people editing the "days left" field manually in the database :)09:51
wolfspraulso from reading some texts (haven't tried it), it looks like the netlist is first exported from eeschema, but when you start working with cvpcb, cvpcb adds new data to it09:51
wpwrak(netlist) yes. there's the issue of merging in the components (footprints)09:51
wolfspraulat that point you do have original data in the netlist09:52
wpwrakcorrect. and it writes its data to a .cmp file as well, for use when the netlist gets redone09:52
wpwrakyou still have it in .cmp. but it's a mess anyway :)09:52
wolfspraulhmm09:52
wolfspraulso when I delete the .net file, it can recreate it, but only if I first export it again from eeschema and pvpcb still has its .cmp file?09:53
wolfspraulI mean recreate without manual intervention09:53
wpwrakmuch like the "last application" field in the profile. each time you run anything, that silly field gets updated and with it the file timestamp. so you almost always have an uncommitted change in the profile. highly annoying09:53
wpwrakyes, that would be the process09:54
wolfspraulthen the .net file including footprints is imported into pcbnew?09:54
wpwrakyup09:55
wolfspraulpcbnew will only read it once, then store the board data in its own files?09:55
wpwrakhmm. not sure. trying ...09:55
wpwrakyeah, remembers the netlist somewhere09:56
wolfspraulor will pcbnew want to open the .net file w/ footprints every time you open the board?09:59
wolfspraulah sorry I should try myself...09:59
wolfspraulI'm just reading through all this trying to make sense of it.09:59
wolfspraulthe KiCad bom file that boom starts with is coming from pcbnew? I can only see a .csv bom export there, is it that one?09:59
wolfspraulhmm, OK09:59
wolfspraulso the .net is really a 'transient' file, for all parties09:59
wolfspraullike a hub09:59
wolfspraul:-)09:59
wolfspraulmy client shows several minutes lag, not sure this gets through...09:59
wolfspraulanother question - what is the workflow with fped? fped has a .fpd file, how does the .fpd file relate to the .cmp and .net files in the normal cvpcb process?09:59
wolfspraulis fped used before/after/instead of pcpcb?10:00
wolfspraulsorry pvpcb10:00
wpwrak(bom) comes from eeschema10:00
wpwrak(lag) it arrived in a big wave :)10:00
wpwrakfped generates .mod files, nothing to do with .cmp and .net10:01
wpwrakthe netlist says how things connect electrically. cmp says which component (U1, R123, etc.) has which footprint (0603, 256BGA, etc.)10:02
wpwrak.mod files define the drawings on the various layers that make up the footprint. and it also defines where the pins/pads are located.10:03
wpwrakfped -k infile.fpd outfile.mod  converts from .fpd to .mod (or you can do it interactively with File>Write KiCad)10:04
wpwrak(waiting for your lag :)10:04
wpwrak... or disconnect :)10:05
wpwrak;-)10:07
wpwrakdesperate means :)10:07
wolfspra1lnot much better, oh well10:08
wpwraki'll retransmit10:09
wpwrak(bom) comes from eeschema10:09
wpwrak(lag) it arrived in a big wave :)10:09
wpwrakfped generates .mod files, nothing to do with .cmp and .net10:09
wpwrakthe netlist says how things connect electrically. cmp says which component (U1, R123, etc.) has which footprint (0603, 256BGA, etc.)10:09
wolfspra1lyes, didn't see it in the menus but I do see it as a toolbar icon now10:09
wpwrak.mod files define the drawings on the various layers that make up the footprint. and it also defines where the pins/pads are located.10:09
wpwrakfped -k infile.fpd outfile.mod  converts from .fpd to .mod (or you can do it interactively with File>Write KiCad)10:09
wpwrak(waiting for your lag :)10:09
wpwrak* wolfspraul has quit (Ping timeout: 265 seconds)10:09
wolfspra1ldo you leave the default settings in the bom export dialog in eeschema?10:10
wpwrakyes, i think i do10:10
wolfspra1lI have checked, by default: Components by reference, Components by value, Output format: List10:11
wolfspra1leverything else is unchecked10:11
wpwrakmost important: footprint and all user-defined fields10:11
wolfspra1lunchecked or checked?10:11
kristianpaulwolfspra1l: hey10:12
wpwrakchecked10:12
kristianpaulsorry replied in wrong channel10:12
kristianpaulwolfspra1l: (rename)  sure go ahead10:12
wolfspra1loh10:12
wolfspra1lthey are unchecked by default10:12
wolfspra1lyou say they should all be checked?10:12
wolfspra1lFootprings, and All existing users fields?10:13
wpwrakah, interesting. here they are checked. System Field: Footprint and Users Fields: All existing users fields10:13
wolfspra1lthere is also a separate list of User Field 1..8, but I guess they are included in 'All existing users fields'10:13
wpwrakyup10:14
wolfspra1lI will try to switch to your bzr 2448 version asap, just haven't gotten to it yet10:14
wolfspra1ldo you know that there is also a bom export in pcbnew?10:15
wpwrak(let's hope these settings are not some obscure per-user preferences. kicad has its defaults scattered over a bit too many places for my taste)10:15
wpwrakis there ?10:15
wolfspra1lyes File -> Fabrication Outputs -> BOM file10:16
wolfspra1lactually the one in (my) eeschema has no menu item, toolbar icon only, argh10:16
wolfspra1lI need to watch every little button and icon in KiCad10:16
wpwraknice :) didn't know that one. naturally, the format is different as well ;-)10:17
wolfspra1lwell10:17
wolfspra1ldon't complain10:17
wolfspra1lif KiCad has an obsession with myriads of different file formats, I think boom is a strong contender10:18
wpwraki'm doing my worst :)10:18
wpwrakalas, there are really tons of different things that go into BOM processing. i could hide a few, but only about 1-210:20
wolfspra1lno no it's good10:20
wolfspra1lyou try to keep separate things separate, let the computer do some work10:20
wolfspra1lit's good10:20
wolfspra1lkristianpaul: renamed, thanks10:21
wolfspra1lyou could add storage costs (for inventory you already own), hey, even currency fluctuations! :-)10:23
wolfspra1lat some point the weather forecast will require less computational power than boom trying to squeeze out the last penny10:23
wpwrakyeah. all those n-dimensional optimization problems have very interesting computational complexity :)10:24
wpwrak(currency) boom keeps currencies apart. if you buy from digi-key and farnell, you get your shopping list with a total in USD and UKP. for deciding what's cheaper, i think i just compare the numbers :)10:25
wolfspra1lyou can try xe.com maybe they have a nice API10:26
wolfspra1l:-)10:26
wolfspra1lif you like10:26
wolfspra1labout EDIF - so it's totally dead for our purposes?10:26
wolfspra1lI saw the syntax having a lot of parentheses, and you mentioned a new KiCad format would be lisp-like...10:27
wolfspra1ldoes KiCad support any edif import or export?10:27
wolfspra1lor can I just totally forget about EDIF?10:27
wpwrak(edif) the format kicad will migrate to looks similar. but i think many of the ideas are based on some other proprietary format. at least for the board files.10:27
wpwrakcomponents (symbols) may be new semantics, also in a lisp-ish syntax. so in a very indirect way, there may be an EDIF influence10:28
wpwrakbut i'll be kicad-"openly proprietary" in the end10:29
wpwrak(xe.com) i'll pass :) if you crave perfection, you also need the exchange rate that gets applied to you, not some interbank rate :)10:30
wolfspra1lyou mean "it'll be openly proprietary" or "I'll be openly proprietary"?10:31
wolfspra1lwell I would assume the format will be all open, no? you mean they borrowed some ideas from a proprietary format?10:31
wpwrak"it'll" :)10:32
wpwrakit'll be proprietary in the sense that it's defined via a product (kicad)10:32
wpwraki'll be open in the sense that you can of course find out how it works. there will also be documentation.10:33
wolfspra1lthe one they have now is not kicad-specific?10:34
wolfspra1lor you just mention the 'proprietary' aspect because I mentioned EDIF?10:34
wpwrakthe current one is of course VERY kicad-specific :)10:34
wpwrak(prop vs. edif) yup10:35
wolfspra1lk logging out for the day10:38
wolfspra1ln810:38
wpwrakcya10:38
qi-bot[commit] Andres Calderon: 1. GPIO connector changed from 2.54mm to 2.0mm pitch http://qi-hw.com/p/xue/609a4fc11:35
qi-bot[commit] Andres Calderon: Routing from the FTDI chip to the AVR Tiny http://qi-hw.com/p/xue/5e9b8d312:31
qi-bot[commit] Andres Calderon: AVR to FTDI conections has been routed http://qi-hw.com/p/xue/c3daabb13:01
kristoffer_wpwrak, you dont happen to know the difference between the different bitblitting operations?14:52
wpwrakkristoffer_: oh, i don't even know where to look for different bitblitting ops :)14:57
kristoffer_wpwrak, nevermind I think I understand now :)14:58
wpwrakkristoffer_: but if it's something in some data sheet (?), perhaps i could help with interpreting it14:58
wpwrak(understand) even better ! :)14:58
kristoffer_wpwrak, I was trying to figure out the difference between copyarea vs imageblit, but think I got it :) Havent worked on the driver in a year and its always weird looking at the docs again15:04
qi-bot[commit] Juan64Bits: Routing FTDI http://qi-hw.com/p/xue/afff77e17:08
qi-bot[commit] Werner Almesberger: Added sanity check for characteristics and corrected omissions/errors found. http://qi-hw.com/p/eda-tools/bf2e9f217:29
qi-bot[commit] Werner Almesberger: Added AVX general-purpose ceramic SMT capacitors, "no series" http://qi-hw.com/p/eda-tools/d816e8217:29
qi-bot[commit] Werner Almesberger: dist/dk/Makefile (count): new target to count the number of parts we have http://qi-hw.com/p/eda-tools/1f52cc917:29
qi-bot[commit] Werner Almesberger: Added Johanson general-purpose ceramic SMT capacitors. http://qi-hw.com/p/eda-tools/f0df99417:29
qi-bot[commit] Werner Almesberger: Added Johanson RF capacitors. http://qi-hw.com/p/eda-tools/94de4f917:29
qi-bot[commit] Werner Almesberger: test.sub now better catches typos and supports more capacitor parameters. http://qi-hw.com/p/eda-tools/d31ede817:29
qi-bot[commit] Werner Almesberger: boom/mbq2lst: recognize #END comment (as end of file, like in the BOOM parser) http://qi-hw.com/p/eda-tools/b55202617:29
qi-bot[commit] Werner Almesberger: Added more detailed part counting. http://qi-hw.com/p/eda-tools/36048db17:29
qi-bot[commit] Werner Almesberger: Introduce temperature coefficients for resistors. http://qi-hw.com/p/eda-tools/5c6ffda17:29
qi-bot[commit] Werner Almesberger: Added Stackpole RNCP series of low TC resistors. http://qi-hw.com/p/eda-tools/03e1fde17:29
qi-bot[commit] Werner Almesberger: Added Yageo RT series of precision chip resistors. http://qi-hw.com/p/eda-tools/ba9a79e17:29
qi-bot[commit] Werner Almesberger: For consistency, renamed captol.inc to ctol.inc. Rs now use rtol.inc instead of http://qi-hw.com/p/eda-tools/6ce7ea117:29
qi-bot[commit] Werner Almesberger: Separate the test from the boom/ top-level directory. http://qi-hw.com/p/eda-tools/61bfa8319:49
qi-bot[commit] Werner Almesberger: more http://qi-hw.com/p/eda-tools/281dda519:49
qi-bot[commit] Werner Almesberger: Generate script boom-config that lists all the database paths, like pkg-config http://qi-hw.com/p/eda-tools/0a86c1019:49
qi-bot[commit] Werner Almesberger: It's now easy to get a list all the files, so we don't need dist/all.* anymore. http://qi-hw.com/p/eda-tools/41ae00919:49
qi-bot[commit] Werner Almesberger: Make boom-config complain about usage errors. http://qi-hw.com/p/eda-tools/9e9eb8919:49
qi-bot[commit] Werner Almesberger: eda-tools now has all the R and C we need here. Removed local database. http://qi-hw.com/p/ben-wpan/265ba0719:49
qi-bot[commit] Werner Almesberger: Use prettyord -t plus a tiny bit of shell to do what SHOW_PRETTY did. http://qi-hw.com/p/ben-wpan/2dec64619:49
wolfspraulwpwrak: feedback about boom/README (svn om location): in line, it says "reference number" but in most other places it says "part-number", if that's what you mean here21:17
wolfspraulsorry line 26221:17
wolfspraulalso it first says "supplier" and then (namespace), everywhere else it just says "namespace" which is explained earlier.21:18
wolfspraulbut why is it reference number and not part-number?21:18
wpwrakjust a small inconsistency :)21:25
wpwrakthe key here is that each item is identified by the name of the name space plus the name in that name space. kinda like directory/file21:26
wolfspraulsure, I did get it, but since all other places say 'namespace part-number' group, I guess it shouldn't be 'reference number' here21:28
wolfspraulunless you fell at that point whoever is actually reading this should be subjected to a little confidence test21:28
wpwrakas i said, an inconsistency. not one that'll live much longer :)21:30
wolfspraulthe documentation is great, no worries21:30
wolfspraulI've seen much worse21:30
wolfspraulit's actually possible to read through the and get a good start - nice21:31
wolfspraulsome of those perl scripts are quite complex21:31
wolfspraulI hope that there will be little need to modify them, in other words that they are properly abstracted from 'simpler' concepts like stock levels, costs, etc.21:32
wolfspraulI think they are, so that's good.21:32
wolfspraulif every little stock inconsistency or the inevitable unforeseen/manual intervention will force someone to go into those complex perl scripts, then the system as a whole will become unusable21:33
wolfspraulof course you know that already, just my feedback after starting to read...21:33
wolfspraulI remember when I watched gta02-core from the distance I saw you working on this bom stuff and I thought now you are completely nuts.21:34
wolfspraul:-)21:34
wolfspraulbut alas, I was wrong21:34
wpwrak(nasty perl) don't worry, all those perl scripts are doomed. the algorithms will get a lot more complex and things need to get more efficient. so all this will have to become C. well, except some external interfaces, digi-key catalog queries and such. they can be in any language.21:36
wpwrak(though there are performance issues as well - the way i currently cache queries has a O(n^2) rebuild-from-cache complexity. not nice.)21:36
wpwrak(nuts) heh ;-)21:37
wolfspraulI didn't know you were that familiar with Perl.21:37
wolfspraulI mean that's a level where the casual copy/paste approach to 100 different scripting languages won't work anymore.21:37
wpwrakthere's a fair amount of "new" perl i used there. for the nested data structures.21:38
wpwrakotherwise, it would have been completely unmanageable21:39
wpwrak(copy&paste) naw, the core needs a real language. also the parser for .sub files is quite marginal. full of hacks to keep it from falling over.21:40
wpwrakand it does get confused in some cases. luckily, so far not confused enough to cause real trouble :)21:40
wpwrakanyway, that's really a job for lex and yacc.21:41
wpwrakREADME fixed. thanks !21:43
wolfspraulwpwrak: is the format you expect to get from the kicad bom (.lst file) documented anywhere?23:39
wolfspraulfor example do you assume that each reference is unique?23:39
wolfspraulyesterday I told you by default I have both 'components by reference' as well as 'components by value' checked by default23:44
wolfspraulthat creates 2 lists, just after each other23:44
wolfsprauldo you need the 'components by value' list? or should that in fact be unchecked?23:44
wolfsprauland since we are at it - the checkbox "Sub components" is unchecked by default for me, I guess that is right...23:46
wolfspraulwhat are the reasons for not using the .csv bom that comes out of pcbnew (other than you not being aware of it and having implemented the parsing for .lst already)23:54
wolfspraulthe good about the .csv out of pcbnew is that there is no dialog, i.e. less things to do wrong23:54
wolfspraulI don't like that Quantity field, seems redundant to the comma separated Designator field (I'm talking about the columns in the .csv bom)23:55
wolfspraulother than that it looks like the .csv also has all data boom needs?23:55
--- Mon Oct 18 201000:00

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