| wolfspra1l | wpwrak: I want to kick the wpan in shape a little | 00:41 |
|---|---|---|
| wolfspra1l | first step is to cleanup the patches inside openwrt so that it can work on other routers too | 00:42 |
| wolfspra1l | do you have any guidance as to what's the best thing to do next there? | 00:42 |
| wolfspra1l | xiangfu: what are your plans? | 00:42 |
| wpwrak | hmm, i should finish the new driver then. and see what things have happened on linux-zigbee since. haven't touched any of this in months. | 00:43 |
| wolfspra1l | wait wait, I don't want to distract you | 00:43 |
| wolfspra1l | :-) | 00:43 |
| wpwrak | (new driver) i.e., make atusb fast enough that it can handle TCP over dirtpan | 00:43 |
| wolfspra1l | I need boom urgently | 00:43 |
| wolfspra1l | much more important from my side | 00:43 |
| wolfspra1l | but I think it's the right thing to move the patches in openwrt such that it can easily work on a router, no? | 00:44 |
| wolfspra1l | that's an easy thing to do | 00:44 |
| wpwrak | depends a bit on the state of the rest of 802.15.4 framework | 00:45 |
| wpwrak | if not much has changed, then it should be relatively easy | 00:45 |
| xiangfu | I have moved the atUSB patches to target/xburst. | 00:46 |
| xiangfu | now needs cleanup and move to linux/generic for all router that have usb host. | 00:46 |
| xiangfu | wpwrak, I haven't test atUSB under OpenWrt. but for now. atBen works just fine. | 00:46 |
| wolfspra1l | xiangfu: yes, sounds great! | 00:47 |
| wolfspra1l | so we can make it work between a ben and a router | 00:47 |
| xiangfu | yes. | 00:48 |
| wolfspra1l | perfect | 00:48 |
| wpwrak | xiangfu: atusb has the problem that it needs to many (slow) round-trips between host and board to actually send a packet. that causes it to run into problems with TCP very quickly. as long as a higher layer implements what amounts to half-duplex communication, it's fine, though. (just a little slow) | 00:49 |
| wpwrak | atben, on the other hand, doesn't have USB in the way to slow it down, and doesn't suffer such issues | 00:51 |
| wpwrak | it can still experience trouble (like stalled connections) | 00:52 |
| wpwrak | but that has other reasons, not really in the domain of the things i've done | 00:52 |
| wpwrak | (although one could alleviate them a bit by forking the at86rf23x driver) | 00:53 |
| wolfspra1l | I don't have a particular use case in mind right now | 00:53 |
| wolfspra1l | I just want to keep the work in a maintainable state, rather than the patches/drivers falling into coma | 00:53 |
| wolfspra1l | but yes, I hear you | 00:53 |
| wolfspra1l | "usb to slow it down" | 00:54 |
| wolfspra1l | :-) | 00:54 |
| wpwrak | maybe a good time would be once the driver is updated. then atusb should work quite smoothly. and then we can pimp it more efficiently ;-) | 00:54 |
| wpwrak | (usb to slow it down) the problem is that the host controller (UHCI, OHCI, etc.) does transfers in 1 ms slots | 00:54 |
| wpwrak | this means that you only get one round-trip communication in one slot, even if the actual dialog takes only a few usecs | 00:55 |
| wpwrak | and the atusb driver spend 99.something % of its time patiently waiting for the next slot ... | 00:56 |
| wolfspra1l | yeah but on the urgency scale, I need boom | 00:56 |
| wolfspra1l | I want to source m1r4 with boom, or compare sourcing status (what we have already) and what's missing with it, etc. | 00:56 |
| wpwrak | yup. i agree. boom first :) just explaining what's amiss with wpan | 00:56 |
| wolfspra1l | yes, perfect | 00:56 |
| wolfspra1l | xiangfu will start by moving things in a better place in openwrt | 00:56 |
| wolfspra1l | that's a small practical step to make the work more accessible | 00:56 |
| kristianpaul | wolfspra1l: had you noticed last dash7 news? | 00:57 |
| kristianpaul | just filling http://www.dash7.org/index.php?option=com_content&view=article&id=222&Itemid=214 | 00:59 |
| wolfspra1l | no, thanks for posting | 01:01 |
| kristianpaul | good, i was re-organizing my stuff today and found rfm12b stuff and tought i dash and found this | 01:02 |
| wpwrak | their lawyers don't seem to believe in the simplicity of "click here to download the PDF" :) | 01:04 |
| kristianpaul | wpwrak: :) | 01:04 |
| qi-bot | [commit] Adam Wang: changed VDDPLL, VDDRCV, VDDRX to input instead of Power input since a common power network generates local net/lable as usual. (master) http://qi-hw.com/p/kicad-libs/e6d4981 | 01:34 |
| qi-bot | [commit] Adam Wang: changed FLG1/2 pins to output/Line. (master) http://qi-hw.com/p/kicad-libs/be5f5bf | 01:43 |
| qi-bot | [commit] Adam Wang: changed HSWAPEN to input which pin controls the internal pull-up resistors on all of the user I/O pins from power-on through completion of configuration. A Low level applied to the pin during configuration enables the internal pull-up resistors, while a High level disables them. (master) http://qi-hw.com/p/kicad-libs/18ae19f | 02:03 |
| cladamw_ | xiangfu, i want to cancel this http://projects.qi-hardware.com/index.php/p/kicad-libs/source/commit/e6d4981d391fef106b88369d1fb85d51e7264b76/ how to use cmd ? like git checkout e6d4981d391fef106b88369d1fb85d51e7264b76 ? | 02:22 |
| xiangfu | cladamw_, git revert e6d4981d391fef106b88369d1fb85d51e7264b76 | 02:23 |
| cladamw_ | so this 'revert' will also change my local file back, right ? | 02:24 |
| xiangfu | cladamw_, yes. | 02:28 |
| cladamw_ | xiangfu, okay. tks. :) | 02:28 |
| xiangfu | cladamw_, it will only change the local file. as long as you don't run 'git push' | 02:28 |
| cladamw_ | xiangfu so the git server will still have last commit existed there since I just did 'revert' and i see that commit history still on there, right ? | 02:31 |
| xiangfu | right. git revert it like: commit1(e6d4) --> commit2(be5f) --> commit3(18ae1), it will only revert commit1. keep the commit2 and commit3. | 02:34 |
| xiangfu | s/it/is | 02:34 |
| qi-bot | [commit] Adam Wang: Revert "changed VDDPLL, VDDRCV, VDDRX to input instead of Power input since a common power network generates local net/lable as usual." (master) http://qi-hw.com/p/kicad-libs/6291bf5 | 02:52 |
| qi-bot | [commit] Adam Wang: pwr.lib : added VIDEOIN_A3V3, VIDEOIN_A1V8, ETH_A3V3, ETH_A1V8, ETH_PLL1V8 for application power. (master) http://qi-hw.com/p/kicad-libs/1bff27c | 02:52 |
| qi-bot | [commit] Adam Wang: pwr.lib : added IR_PWR, VAA_3V3 for application power. (master) http://qi-hw.com/p/kicad-libs/e117f71 | 03:57 |
| qi-bot | [commit] Werner Almesberger: components/EXPAND: added latest application-specific power symbols (master) http://qi-hw.com/p/kicad-libs/dec1eee | 07:18 |
| qi-bot | [commit] Adam Wang: changed to upper case. (master) http://qi-hw.com/p/kicad-libs/cf35956 | 07:28 |
| qi-bot | [commit] Adam Wang: Merge branch 'master' of projects.qi-hardware.com:kicad-libs (master) http://qi-hw.com/p/kicad-libs/e33b87a | 07:28 |
| cladamw | wpwrak, before i do KiCad patch http://projects.qi-hardware.com/index.php/p/eda-tools/source/tree/master/kicad-patches/README, do I need to un-install somethings ? | 08:28 |
| wpwrak | you may have to uninstall kicad when you reach the point of installing | 08:30 |
| wpwrak | but you can even test it first | 08:30 |
| wpwrak | so once you've compiled everything, you can, for example, start the new eeschema with /your/path/kicad/eeschema/eeschema | 08:31 |
| wpwrak | then see if it looks right | 08:31 |
| wpwrak | then, apt-get remove kicad (or similar, depends on how you installed your present kicad) | 08:31 |
| wpwrak | then make install | 08:32 |
| cladamw | i see a file "kicad.bzr" after "bzr checkout -r 3494 lp:kicad kicad.bzr" so keep following your README now i think. :) | 08:32 |
| wpwrak | then open a new xterm (or do PATH=$PATH), launch eeschema again, then check that the version is right | 08:32 |
| cladamw | okay, need to try. :) | 08:33 |
| wpwrak | very good. make the path above then /your/path/kicad.bzr/eeschema/eeschema :) | 08:33 |
| wpwrak | kicad is pretty friendly when it comes to installation. the hard part is getting it to compile at all ;-) | 08:34 |
| cladamw | alright | 08:34 |
| cladamw | wpwrak, the current latest m1r4 whole schematic i fixed it now leaves TWO warnings only, I can't figure them out why. | 08:36 |
| wpwrak | let's see | 08:37 |
| cladamw | phew~ from 66 warnings down to todays' last two wanings. :) so I would to use your this latest patches, then check it again hope I install successfully. | 08:38 |
| wpwrak | two warnings is a good value for such a large design | 08:38 |
| wpwrak | hah, i get 16 warnings ;-) | 08:38 |
| cladamw | i haven't uploaded all files( kicad-libs/components, and milkymist/board-m1/r4) | 08:39 |
| cladamw | so maybe that you just got 16 warnings. :-) | 08:39 |
| wpwrak | then i misread your "I can't figure them out why" :) | 08:40 |
| wpwrak | chances are that the new eeschema will find more rather than less. there's a general tendency that warnings get added, hardly ever removed :) | 08:41 |
| cladamw | wpwrak, ha... well... must be haven some tricky ways to cheat DRC/eeschema to pass them. :-) | 08:42 |
| cladamw | there's much funny things I re-edited different ways to let free warnings and passed, you will see. funny though ! | 08:44 |
| cladamw | but I can't rely on my older version. so later we know. :) | 08:44 |
| wpwrak | sometimes there are indeed "invisible" problems. such as a net that looks as if it was connected but isn't. | 08:47 |
| wpwrak | hmm, all these board-specific power symbols are a bit troubling | 08:48 |
| wpwrak | alas, kicad more or less forces you to do things that way :-( | 08:48 |
| wpwrak | since you can't rename a power symbol in the schematics | 08:49 |
| qi-bot | [commit] Adam Wang: changed ADV7125KSTZ140's pin 13/29/30 to input (master) http://qi-hw.com/p/kicad-libs/f8b3e2d | 08:50 |
| cladamw | wpwrak, yeah .... about power symbols i got troubles | 08:52 |
| cladamw | wpwrak, but wait a bit. lemme uploaded all files, then you could check them again to see if same two warnings left. :) | 08:52 |
| cladamw | wpwrak, done. :) I just committed all my files here. so you may check to do DRC, and if also get two warnings on J17's pin 20 and 21. :) | 08:56 |
| wpwrak | 11 errors/warnings | 08:56 |
| cladamw | wpwrak, to me. then i do horrible patches steps myself. :-) | 08:57 |
| cladamw | wpwrak, man! 11 ! | 08:57 |
| wpwrak | did you change anything in the ERC options ? i'm not sure if they're saved with the project | 08:57 |
| cladamw | no, i didn't touch KiCad's settings/default .:-) | 08:59 |
| cladamw | check this: http://dpaste.com/736030/ | 08:59 |
| cladamw | wpwrak, me either, don't know if DRC settings saved in which file. :) | 09:00 |
| wpwrak | i don't get that one | 09:00 |
| cladamw | well .... okay, you can try to fix them if have time. but no rush. i should install yours patches work now. :-) | 09:01 |
| wpwrak | ah wait. once | 09:01 |
| wpwrak | http://downloads.qi-hardware.com/people/werner/tmp/m1.erc | 09:02 |
| cladamw | aha.. nice ! I'll go back to see your this result compared to the one after I installed. :) | 09:04 |
| wpwrak | there are PWR_FLAG symbols in the schematics that come up as ??, so they're not in kicad-libs | 09:05 |
| wpwrak | that may explain most of the errors/warnings | 09:08 |
| cladamw | but why in here, i didn't get yours err even I found the PWR_FLG (under KiCad's system power.lib) wasn't inserted m1.pro ? | 09:10 |
| cladamw | wpwrak, btw, what's this meanings. "ln -s wherever/eda-tools/kicad-patches patches" ? | 09:11 |
| wpwrak | wherever means there you've placed eda-tools/... (from qi-hw) | 09:12 |
| wpwrak | this creates a symbolic link from patches -> eda-tools/kicad-patches/ | 09:12 |
| wpwrak | which in turn quilt uses to find the patches | 09:12 |
| cladamw | adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ ln -s ~/eda-tools/kicad-patches patches | 09:16 |
| cladamw | ln: creating symbolic link `patches': File exists | 09:16 |
| wpwrak | then you've already done it | 09:16 |
| wpwrak | if you did it wrong the first time, rm patches and try again | 09:17 |
| wpwrak | hmm, i think we should make our version of "PWR_FLAG" a bit more explicit that the original. lemme try ... | 09:18 |
| cladamw | there's four 'cmdline-*.patch under adam@adam-laptop:~/eda-tools/kicad-patches$ | 09:18 |
| wpwrak | quilt patch -a | 09:18 |
| wpwrak | quilt takes care of the rest :) | 09:18 |
| cladamw | wait:) | 09:19 |
| wpwrak | (the link is to the directory. so, when in kicad.bzr, ls patches should also show you the files in eda-tools/kicad-patches/) | 09:19 |
| cladamw | type "quilt patch -a" under adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ or ~/eda-tools/kicad-patches/ ? | 09:19 |
| wpwrak | under kicad.bzr | 09:21 |
| cladamw | yeah ... i found and now install 'quilt' :( | 09:22 |
| wpwrak | hah ! :) | 09:25 |
| cladamw | wpwrak, so like this ? and run each *.patch one-by-one ? adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ quilt ~/eda-tools/kicad-patches/cmdline-common.patch -a | 09:27 |
| wpwrak | no | 09:28 |
| wpwrak | quilt push -a | 09:28 |
| cladamw | wpwrak, yes, i agreed that making our own version of "PWR_FLG". | 09:28 |
| wpwrak | just do as the README says :) | 09:28 |
| cladamw | adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ quilt push -a | 09:28 |
| cladamw | No patches in series | 09:28 |
| wpwrak | then your link has a problem | 09:29 |
| wpwrak | rm patches | 09:29 |
| wpwrak | ln -s ~/eda-tools/kicad-patches patches | 09:29 |
| wpwrak | then try again | 09:29 |
| cladamw | nice! | 09:30 |
| cladamw | done ? http://dpaste.com/736042/ | 09:30 |
| cladamw | i keep following README. :) | 09:31 |
| wpwrak | victory is yours ! :) | 09:31 |
| cladamw | http://dpaste.com/736044/ | 09:32 |
| qi-bot | [commit] Werner Almesberger: components: added powered.lib (POWERED), to replace PWR_FLG (master) http://qi-hw.com/p/kicad-libs/43585b4 | 09:32 |
| cladamw | building seems slow. | 09:34 |
| wpwrak | hmm, something's not right with "powered" .. | 09:34 |
| wpwrak | (slow) it's C++ ... | 09:35 |
| cladamw | wpwrak, i found eechema will everytimes changes *.sch once i used system's PWR_FLG and fixed err, the PWR??? (??? means number ) will always be changed. I don't know how eescheme it works. you can check for a while. :) | 09:37 |
| wpwrak | uh, these numbers may not mean a lot | 09:38 |
| cladamw | since i've seen they are auto changed. :) | 09:40 |
| cladamw | maybe sschema manages internal pwr net, etc. :-) | 09:40 |
| wpwrak | with proper power flag, still 9 errors | 09:44 |
| cladamw | green or blue ? | 09:46 |
| wpwrak | uh ? | 09:46 |
| cladamw | green(warings) blue (err) :) | 09:46 |
| cladamw | 9 errors includes green and blue ones. :) | 09:46 |
| wpwrak | didn't look at the markers. it counts 9 errors and 9 warnings | 09:47 |
| cladamw | wow..okay | 09:47 |
| cladamw | actually they should be easiler to fix. :) | 09:47 |
| wpwrak | e.g., FLASH_A0 ... A3 no connected | 09:47 |
| wpwrak | hmm. you have an A2 sheet in there ? :) | 09:49 |
| cladamw | yes | 09:49 |
| cladamw | since FPGA.sch is too large. :) Is it to related ? | 09:49 |
| wpwrak | naw. but it's too big. maybe one can still read A3 when printing, but A2 would be tiny | 09:50 |
| cladamw | we can split it into two A3 sheet if it's not displayed well for you. :) | 09:50 |
| wpwrak | yes, we should keep sheet sizes reasonable. i'm not even entirely sure about A3 ... | 09:51 |
| cladamw | hmm...sounds you're right. then we seperate A2 into two-A3 later. | 09:51 |
| wpwrak | i would also rename some of the sheets. don't name them by component but by function. | 09:52 |
| wpwrak | e.g., not "ADV7181CBSTZ" but "Video In" | 09:53 |
| wpwrak | same for micel, micron, xilinx, wolfson, the other analog devices, numonix | 09:53 |
| cladamw | am i finished ? http://dpaste.com/736056/ | 09:54 |
| wpwrak | ah, s/rename/relabel/. in the overview sheet. the file names look okay | 09:54 |
| cladamw | wpwrak, sure ... okay. :) | 09:54 |
| wpwrak | but you hardly see them (the file names) on the big sheet :) | 09:54 |
| wpwrak | (build_ looks great | 09:55 |
| cladamw | wpwrak, yeah....needs to think another way to display text bigger for "Video In" "Audio In/Out" etc ... | 09:55 |
| wpwrak | now launch eeschema and check help / about eeschema | 09:55 |
| cladamw | i found text can't be placed within in eeschema's hierarchical rectangle. so need to study more. or you know how to. :) | 09:56 |
| wpwrak | (bigger text) i would just not mention the chips at that point. that's not really useful information there, and when we change a chip, you'll always have to remember to change it in the overview, too. | 09:57 |
| wpwrak | it can't ? i though it could. checking .. | 09:57 |
| wpwrak | works fine for me :) | 09:58 |
| wpwrak | it is hard to do things with it there, though. e.g., you can't easily move it around | 09:58 |
| cladamw | i tried to place text within that hierarchical rectangle but not. | 09:58 |
| cladamw | yeah | 09:58 |
| cladamw | oah..nice ! yours can do it. :) | 09:58 |
| wpwrak | yours too :) | 09:59 |
| wpwrak | did you check the version ? just run eeschema | 09:59 |
| cladamw | wait. help me to finish the PATH | 09:59 |
| wpwrak | you mean PATH=$PATH ? | 10:01 |
| cladamw | i typed "eeschema" under adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ but it's older one(BRZ 2448), so how to set PATH ? | 10:01 |
| cladamw | yes | 10:01 |
| wpwrak | try which eeschema | 10:02 |
| cladamw | /usr/local/bin/eeschema | 10:02 |
| wpwrak | interesting. that's where you've just installed the new version | 10:02 |
| cladamw | yes. then ... ? | 10:02 |
| cladamw | :) | 10:03 |
| wpwrak | okay, PATH=$PATH | 10:03 |
| wpwrak | then eeschema again | 10:03 |
| wpwrak | if you still get the old version, try | 10:03 |
| cladamw | nice ! now 3494 :) | 10:03 |
| wpwrak | .... not needed :) ... | 10:04 |
| wpwrak | perfect ! ;-) | 10:04 |
| cladamw | (2012-0408 ZR 3494)-testing | 10:04 |
| wpwrak | now you can try to see for yourself what errors are there :) | 10:04 |
| cladamw | wpwrak, tks for your helps. and the new GUI is amazing though. :) | 10:05 |
| wpwrak | unfortunately, it also has a few quirks | 10:05 |
| wpwrak | you'll see. e.g., when dragging. that's now a bit inconvenient and takes a while to get used to | 10:06 |
| cladamw | wpwrak, INTERESTING! I got still those two warning! | 10:07 |
| wpwrak | that suggests that you didn't commit all your files :) | 10:09 |
| cladamw | really? wait. i need to upload my DRC default settings to compare to yours. | 10:10 |
| qi-bot | [commit] Werner Almesberger: components/powered.lib: reduced pin length (master) http://qi-hw.com/p/kicad-libs/867b8f9 | 10:12 |
| wpwrak | maybe start by deleting the cached components. there should be a file *cache*lib | 10:13 |
| cladamw | wpwrak, http://downloads.qi-hardware.com/people/adam/kicad/Erc_settins_3494.png | 10:13 |
| cladamw | (cache) poor adam. okay... go find that lib. :) | 10:14 |
| wpwrak | ERC settings are the same here | 10:16 |
| wpwrak | that lib would be in board-m1/r4/ | 10:16 |
| wpwrak | kicak loves its little caches | 10:16 |
| cladamw | same results after deleted m1-cache.lib and its dcm | 10:19 |
| cladamw | strange | 10:20 |
| cladamw | wpwrak, how to check or type which git cmd to know if I have some files i didn't commit ? | 10:21 |
| wpwrak | here are the .sch files i see: http://pastebin.ca/2139127 | 10:23 |
| cladamw | except those files with timestamps changes I didn't commit, then i always use 'git checkout -- *.lib or *.dcm" after i see there's no differences after typed "git diff filename". :) | 10:23 |
| wpwrak | git diff tells you which files are known and have changes | 10:24 |
| wpwrak | there's one more step: if you add files manually with git add, then they disappear from git diff. you can see them with git diff --cached | 10:24 |
| lindi- | "git ls-files -m" lists modified files if you need them in a reusable format | 10:25 |
| lindi- | and "git ls-files -o" lists files that are not in the repo | 10:25 |
| cladamw | i sured those 15 *.sch I commited | 10:25 |
| cladamw | lindi-, hi nice ! http://dpaste.com/736063/ | 10:27 |
| cladamw | lindi-, much thanks a lot! | 10:27 |
| wpwrak | all files that shouldn't be in git. so this is good. | 10:28 |
| lindi- | of course if you use emacs then I'd suggest magit | 10:28 |
| lindi- | :-) | 10:28 |
| cladamw | maybe i need to delete m1-cache.bak & *.bck ? | 10:28 |
| wpwrak | and you've deleted the cache library. if you run eeschema now, do the errors still appear ? | 10:28 |
| wpwrak | i don't think kicad used .bck or .bak automatically | 10:28 |
| cladamw | wpwrak, no, i still got two warnings only after deleted m1-cache.lib. :( | 10:29 |
| wpwrak | grmbl | 10:29 |
| cladamw | wpwrak, wait. you just updated kicad-lib/component ? so i need to sync ? | 10:31 |
| wpwrak | yeah, why not. it's just the new POWERED symbol | 10:31 |
| cladamw | or it's not related though. don't know | 10:31 |
| wpwrak | lemme update m1-board then, too | 10:31 |
| wpwrak | incoming ... | 10:33 |
| cladamw | okay...lemme do sync and DRC again. :-) | 10:34 |
| cladamw | phew~ still two. | 10:36 |
| wpwrak | you should DRC your components ... | 10:36 |
| cladamw | i saw your new POWERED flg | 10:37 |
| wpwrak | e.g., 74320-1004 produces a lot of complains in the library editor | 10:37 |
| wpwrak | http://downloads.qi-hardware.com/people/werner/tmp/trouble.png | 10:39 |
| wpwrak | seems that some copy & paste went terribly wrong | 10:39 |
| cladamw | wow..nice the new version in Library Editor has DRC function. :-) | 10:40 |
| cladamw | wpwrak, ha ... nice. now i can follow DRC window results to fix it. the older version doesn't have DRC version in Library Editor. phew~ | 10:42 |
| wpwrak | ah, really ? i though that has been around for a while. maybe it was hidden, though | 10:43 |
| cladamw | but still don't know why the DRC results in Schematic editor which are not same as yours ? | 10:43 |
| cladamw | you said you got 9 | 10:43 |
| xiangfu | do you need me? do this DRC again? | 10:43 |
| cladamw | i got two only. phew~ | 10:44 |
| cladamw | xiangfu, wpwrak wait no need now. :-) | 10:44 |
| cladamw | since I need to use this new KiCad version to check components in Library Editor then go back in eeschema to do DRC. :-) | 10:45 |
| wpwrak | yeah :) | 10:45 |
| wpwrak | if it's a commit problem, maybe it'll disappear as part of that cleanup | 10:45 |
| cladamw | but in the parallel , if you both have time, you could do it. but don't do from you both now. | 10:46 |
| cladamw | since I need to figure out why my results got two only and yours is 9 ! :-O | 10:46 |
| wpwrak | i suspect that there's some commit difference. let's see how things look once you're done with the cleanup | 10:47 |
| cladamw | xiangfu, but maybe you can also do patch for KiCad by http://projects.qi-hardware.com/index.php/p/eda-tools/source/tree/master/kicad-patches/README | 10:48 |
| wpwrak | this will probably remove the two ERC warnings/errors you got | 10:48 |
| wpwrak | (this = the cleanup) | 10:48 |
| wpwrak | if we still diverge afterwards, we'll need to try tarballs ... | 10:48 |
| cladamw | wpwrak, yeah... since this board-m1 is my firstly done with frequently git commit, actually i don't know if I did well on git work though. :-) | 10:49 |
| wpwrak | so far, it looks good. oh, and we should track the changes in schhist | 10:49 |
| wpwrak | hmm. http://projects.qi-hardware.com/schhist/ -> You don't have permission to access /schhist/ on this server. | 10:50 |
| wpwrak | :-( | 10:50 |
| cladamw | wpwrak, be careful on my skill on git work now. :) | 10:50 |
| cladamw | so don't open permission unless you think that i'm qualified. :-O | 10:50 |
| wpwrak | schhist is a pretty good detector for commit problems ;-) | 10:51 |
| wpwrak | (permissions) naw, there's something wrong in the setup on project.qi-hw.com | 10:52 |
| wolfspra1l | wpwrak: you want to add board-m1 to schhist? | 10:52 |
| wolfspra1l | I needed to do it anyway... | 10:53 |
| cladamw | xiangfu, wpwrak i think from now on, who wants to contribute this project, should all sync to the latest tools(KiCad patches) how do you think ? | 10:53 |
| wpwrak | cladamw: agreed. if versions are too much out of sync you run into too many little problems | 10:54 |
| cladamw | yeah... | 10:55 |
| cladamw | xiangfu, so please also use latest KiCad patches. :-) | 10:55 |
| xiangfu | cladamw, ok. | 11:05 |
| qi-bot | [commit] Adam Wang: molex.lib: 74320-1004 -> removed duplicated pins (master) http://qi-hw.com/p/kicad-libs/dc58a6f | 12:40 |
| cladamw | [m1r4 DRC Zero err] after last commit on J17 duplicated pins, board-m1 now got zero err after DRC from adam site here. | 12:43 |
| cladamw | now needs to check carefully why mine differs from Werner's. :-) | 12:45 |
| pabs3 | a mention of Milkymist/Nanonote in a blog post (from Fedora Planet) http://karl-tux-stadt.de/ktuxs/?p=3629 | 14:15 |
| qi-bot | The build was successful: http://fidelio.qi-hardware.com/~xiangfu/build-nanonote/openwrt-xburst.full_system-20120422-0824 | 14:28 |
| LunaVorax | Hello everyone. | 18:35 |
| qi-bot | [commit] Werner Almesberger: bin/pidiff: position-independent diff filter (master) http://qi-hw.com/p/wernermisc/9a31615 | 22:34 |
| wolfspra1l | pabs3: oh cool, thanks for posting! | 23:07 |
| pabs3 | wolfspra1l: interesting data point: idling on #opencores I found this presentation which claims OpenRISC commercial deployment has been going on since 2007: http://oshug.org/presentations/openrisc-oshug17-final.pdf | 23:45 |
| wolfspra1l | pah :-) | 23:48 |
| wolfspra1l | I really like your input, but can you speed up and forward to 2012 :-) | 23:48 |
| wolfspra1l | yes sure, there is all that | 23:48 |
| wolfspra1l | orsoc | 23:48 |
| wolfspra1l | etc. | 23:48 |
| wolfspra1l | a company in sweden, one in slovenia I think, and so on | 23:48 |
| wolfspra1l | now... what do you do with that stuff today? | 23:48 |
| wolfspra1l | the answer is probably: nothing | 23:48 |
| wolfspra1l | otherwise you wouldn't read those old news and wonder what it means | 23:48 |
| pabs3 | I hadn't yet heard about that stuff, so yeah | 23:49 |
| wolfspra1l | sure sure | 23:49 |
| wolfspra1l | it's good | 23:49 |
| wolfspra1l | you are on the right path | 23:49 |
| wolfspra1l | also with opensparc etc | 23:49 |
| wolfspra1l | please let me know if I overlook something, but I think the two most active free cores now are openrisc and milkymist | 23:49 |
| wolfspra1l | maybe you should get a milkymist one and enter ic design & hdl :-) | 23:50 |
| wolfspra1l | we try to make something *work* | 23:51 |
| wolfspra1l | no matter how painful that is, it's far better than trading wishlists and empty talk, imho | 23:52 |
| wolfspra1l | so... for example. the milkymist one vga resolution is 640x480 now | 23:52 |
| wolfspra1l | that's as high as we can go | 23:52 |
| wolfspra1l | at 24fps and 16bpp, no less | 23:52 |
| wolfspra1l | get one, feel the pain, let's crank it up. if there is a better free soc, let's use it :-) | 23:53 |
| wolfspra1l | (you will quickly find out that you cannot reflash a press release onto a nor chip :-)) | 23:53 |
| wolfspra1l | someone said they would try porting openrisc to the m1, but I haven't heard back in months | 23:54 |
| wolfspra1l | pabs3: why do you follow this stuff? what are you aiming for? | 23:56 |
| wolfspra1l | I mean the sparc/openrisc/milkymist etc. | 23:56 |
| --- Tue Apr 24 2012 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!
