Back
[00:42:31] <Guest847> Guest847 is now known as skunkworks
[14:37:19] <jepler> wow -- xilinx webpack is now up to a 1.6GB download
[14:50:46] <SWPadnos_> heh - yes indeed. it's a biggie
[14:51:28] <SWPadnos_> and what's really nice is that you need to download that, tehn unpack it, and then you can install (which decompresses it)
[14:51:42] <SWPadnos_> so a system with a small hard drive requires special care :)
[16:55:36] <jmkasunich_> how often do they version bump that xilinx stuff? seems like it will be pain to keep up to date
[17:24:56] <eugenio> hi
[17:30:08] <eugenio> i have just compiled kernel, rtai and emc2 trunk, now I'm going to analize the code, any hint or guide to look before getting dirt my hands?
[17:38:53] <jepler> jmkasunich_: indeed. apparently the last step of installation is to download an additional few hundred megabytes of "service pack". Apparently that adds up to 284MB + 620MB more ..
[17:39:47] <jepler> eugenio: that's too broad a question to really be answerable. If you have specific questions, including "where's the source code that does X", those are much easier to answer.
[17:40:19] <jepler> there's directory.map at the top level, and some musings in docs/src/code but both probably contain outdated information in some instances
[17:40:49] <jepler> use scripts/swish to do a full-text search of the source and documentation trees
[17:41:48] <jepler> if you use a tags aware editor, use "make tags" in the source directory to make the tags file
[17:44:42] <eugenio> thx jepler
[17:51:20] <eugenio> the info in directory.map was what i was looking for
[17:54:58] <eugenio> i am with xilinx ise 7.1, the biggest problem i have is its shitty driver of the jtag for linux
[21:50:54] <christel> [Global Notice] Hi all, we're experiencing some routing problems between our US hub and the machine services reside on, I'm about to do some re-routing and will also move services. There will be NO services while we swap things around. Thank you for using freenode and have a great day!
[22:04:00] <SWPadnos_> SWPadnos_ is now known as SWPadnos
[22:05:17] <jepler> * jepler is compiling the pluto_servo verilog in webpack for the 7i43 as a way to get familiar with ise
[22:05:27] <SWPadnos> heh
[22:05:38] <SWPadnos> get familiar with the "clean project files" menu item
[22:05:57] <jepler> a few source code changes were required, and of course to really run this I'd have to get the pin constraints right
[22:06:16] <SWPadnos> or, if you find out how to turn off that stinking buggy incremental compile feature, please tell me how to do it
[22:06:43] <SWPadnos> was there a UCF file in the 7i43 zip file? (if there is a 7i43 zip file)
[22:06:48] <jepler> is that why on an earlier run it kept saying one stage of my project had encountered an error, and wouldn't proceed?
[22:06:53] <jepler> yes there are some ucf files in there
[22:06:55] <SWPadnos> I don't think so
[22:07:04] <jepler> and yes, the 7i43 zip file is now available
[22:07:09] <SWPadnos> cool
[22:07:38] <SWPadnos> by the way, I'm serious about sending you one. if you want to play around, I think it's a good investment
[22:09:02] <jepler> I dunno if it would ever make it to the top of my list of things to do
[22:09:26] <SWPadnos> no biggie. I know how those lists tend to be like mobius strips anyway ;)
[22:09:50] <jepler> hah
[22:10:16] <jepler> if you're feeling generous I wouldn't turn you down -- but I don't want you to feel you're bargaining for some kind of software to be written for it
[22:10:22] <SWPadnos> nope
[22:10:56] <SWPadnos> it's not a "deal", it's a "gift, with a possible hope of something good coming out of it, whether or not it's good for me"
[22:11:37] <SWPadnos> of course, I haven't ordered any yet, and I'm busy these days, so don't expect to get one on Monday :)
[22:12:25] <jepler> hah
[22:12:34] <jepler> by christmas, maybe
[22:12:41] <SWPadnos> you never know
[22:13:20] <SWPadnos> of course, I'm going to be on the road basically from next Tuesday until the end of the month, then I may be on the road again for a couple of weeks, then we go off for some Christmas trip, and then .......
[22:13:48] <jepler> whatever
[22:15:02] <jepler> anyway, that's very generous of you
[22:15:17] <SWPadnos> heh. I hope it is at least
[22:15:44] <SWPadnos> I think my company will have some money to spend before the end of the year, so I may get a 5-pack or something.
[22:16:03] <SWPadnos> it's nice to be able to deduct expenses for that kind of toy^Wequipment
[22:21:06] <jepler> I am a bit surprised that the speed difference between the acex and the spartan3 is not greater -- the pluto_servo design only gets about 2.2x the clock speed (assuming I correctly remember the timings under altera's software)
[22:21:30] <jepler> .. about 75MHz vs about 180MHz
[22:21:41] <SWPadnos> it's possible that it's limited by the design itself
[22:22:15] <SWPadnos> I think optimization of an FPGA isn't intuitive to a "sequential programmer" - ie us software guys
[22:22:31] <jepler> that's true
[22:22:50] <jepler> I wasn't saying my design was or wasn't inherently good, but that I figured fpga technology was a "rising tide that floats all boats"
[22:22:52] <SWPadnos> conceptually, an FPGA doesn't reuse any "code", so you may as well make everything run in parallel and just select which output you want to use at the end
[22:22:55] <SWPadnos> heh
[22:23:07] <SWPadnos> it did float by a factor of 2.2 :)
[22:23:10] <jepler> indeed
[22:23:21] <jepler> and I notice that the mesanet samples use the high speed grade
[22:23:29] <jepler> I chose the low speed grade
[22:23:33] <SWPadnos> ah
[22:23:35] <jepler> I wonder how much difference that makes
[22:23:47] <SWPadnos> could be another 50% actually
[22:23:58] <SWPadnos> well, 1.5x the 2.2x, so 3.3x
[22:24:18] <jepler> the speed grades are -4 and -5 but I dunno what that means
[22:24:24] <SWPadnos> I think the low speed ones are 6ns, adn the high are 4ns - or it's in that ballpark anyway
[22:24:32] <SWPadnos> that may be ns, but I'm not sure it is
[22:24:51] <SWPadnos> hmmm. no, it probably isn't, because I think there are some -1s
[22:37:23] <jepler> SWPadnos: does the free version of ise benefit from multiple CPUs?
[22:37:33] <jepler> (or multiple cores, to be more accurate)
[22:38:16] <jepler> hi ray
[22:39:33] <rayh> Hi Jeff.
[22:40:52] <SWPadnos> jepler, it didn't look like it, but I may have missed a configuration setting or two
[22:40:56] <SWPadnos> hi ray
[22:42:39] <rayh> Hi Steven
[22:57:23] <CIA-18> 03jepler 07v2_2_branch * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: restore cone-rotating behavior (danielbr misses it)
[22:57:38] <SWPadnos> heh
[22:58:07] <jepler> uh oh, I just did something very different from what I intended
[22:58:08] <CIA-18> 03tissf 07TRUNK * 10emc2/src/po/ (fr.po fr_axis.po fr_rs274_err.po): French translation update
[22:58:19] <jepler> % cvs up -j1.31 -j1.31.2.1 axis.py
[22:58:26] <jepler> cvs commit -m"merge from v2_2_branch: restore cone-rotating behavior" axis.py
[22:58:38] <jepler> new revision: delete; previous revision: 1.131
[22:58:50] <jepler> now, how do I undo this little screwup I just made?
[22:58:56] <tissf> hello all
[22:58:58] <SWPadnos> cradek, help! :)
[22:59:28] <CIA-18> 03compile-farm 07Ubuntu 5.10 (breezy) realtime (2.6.12-magma) * 10emc2head/: build FAILED ; see
http://linuxcnc.org/compile_farm/emc2head_slot2_log.txt
[22:59:34] <jepler> yeah I bet the compile failed!
[22:59:39] <SWPadnos> heh
[23:00:21] <CIA-18> 03compile-farm 07BDI-4.51 (2.6.16.20-rtai) * 10emc2head/: build FAILED ; see
http://linuxcnc.org/compile_farm/emc2head_slot6_log.txt
[23:00:22] <CIA-18> 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: undo incorrect merge that deleted this file
[23:00:25] <CIA-18> 03compile-farm 07Ubuntu 5.10 (breezy) non-realtime (2.6.12-10-386) * 10emc2head/: build FAILED ; see
http://linuxcnc.org/compile_farm/emc2head_slot1_log.txt
[23:01:00] <CIA-18> 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: merge from v2_2_branch: restore cone-rotating behavior
[23:01:21] <jepler> tissf: hi tissf
[23:01:43] <CIA-18> 03compile-farm 07Ubuntu 5.10 (breezy) non-realtime (2.6.12-10-386) * 10emc2head/: build PASSED
[23:01:43] <CIA-18> 03compile-farm 07BDI-4.51 (2.6.16.20-rtai) * 10emc2head/: build PASSED
[23:01:54] <SWPadnos> damn, that's a lot faster now
[23:01:59] <jepler> yeah it is
[23:02:16] <jepler> tissf: the translation updates you made, should they also be made in 2.2.x?
[23:03:21] <jepler> tissf: if so, I can help you learn about using branches in cvs
[23:03:36] <tissf> Yes i think
[23:04:39] <tissf> Just finish a fresh dapper install and emc2.trunk compilation (2 days ! )
[23:04:45] <jepler> tissf: CVS uses branches so that different versions of the software can be maintained. So far, you have always been working with the one called the TRUNK.
[23:05:02] <tissf> yes
[23:05:25] <jepler> tissf: but since the release of emc 2.2.0, there is another branch called v2_2_branch. On that branch, we make only a few kinds of changes: documentation improvements, translation improvements, bug fixes, and new drivers
[23:06:02] <CIA-18> 03compile-farm 07Ubuntu 5.10 (breezy) realtime (2.6.12-magma) * 10emc2head/: build PASSED
[23:06:20] <tissf> jepler: ok I have to work on v2_2_branch ?
[23:06:49] <jepler> tissf: to make changes in v2_2_branch, you first have to get a CVS checkout of the branch. Do that by adding "-rv2_2_branch" to your "cvs co" command, and also give the checkout a distinctive name with the "-d<dirname>" flag
[23:07:24] <tissf> jepler: ok
[23:07:40] <jepler> in that directory, you can use "cvs up" and "cvs commit" like you've already learned
[23:07:56] <tissf> jepler: ok
[23:08:17] <jepler> in most cases you'll first make, test and check in your changes in the TRUNK. then you'll make the same changes in v2_2_branch, test, and check in a second time
[23:08:40] <tissf> jepler: ok
[23:09:31] <jepler> CVS can help you make the same changes in the branch as on the TRUNK. If you noted the old and new version numbers when you committed a file on TRUNK, you can use a special form of "cvs up" to make the same changes in the file on the branch: cvs up -jOLDVERSION -jNEWVERSION filename
[23:10:20] <tissf> jepler: ok
[23:10:21] <jepler> you can use "cvs log" or cvsweb (
http://cvs.linuxcnc.org/cvs/emc2/) to help you find the revision numbers if you didn't note them when you made the first check-in
[23:11:56] <tissf> jepler: ok
[23:13:12] <CIA-18> 03jepler 07v2_2_branch * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: actually restore A-axis rotation of cone
[23:14:40] <CIA-18> 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: merge from trunk: actually restore A-axis cone rotation
[23:15:00] <jepler> tissf: after the special "cvs up", you still have to "cvs commit"
[23:15:56] <jepler> so for instance in the case of fr_axis.po, you would run this command in the src/po directory: cvs up -j1.12 -j1.13 fr_axis.po
[23:15:57] <jepler> then test and commit
[23:16:46] <tissf> jepler: how test ?
[23:17:15] <jepler> tissf: build the software and verify that the new translations appear
[23:17:23] <tissf> jepler: ok
[23:18:13] <tissf> jepler: will do everything
[23:19:15] <jepler> good, thank you
[23:19:59] <tissf> jepler: thank you for help
[23:44:04] <tissf> jepler: the cvs up in the src/po directory but which version? trunk or v2_2_
[23:44:44] <jepler> tissf: in the v2_2_branch directory -- the one that you want to modify
[23:45:02] <tissf> jepler: ok thanks
[23:45:14] <jepler> that "cvs up" just changes the file on your local disk, it doesn't change anything on the cvs server until you commit
[23:45:39] <tissf> jepler: ok
[23:46:36] <tissf> jepler: Silly question sorry!
[23:55:25] <jepler> SWPadnos: seems -5 is the high speed grade and -4 the low one! that's the opposite of what I expected.
[23:55:43] <SWPadnos> ok, I guess that proves the numbers aren't nanoseconds :)
[23:56:02] <tissf> python ../docs/src/lyxtree.py --imagedir=../docs/html -o objects/gui_axis.xml ../docs/src/gui/axis.lyx
[23:56:06] <tissf> # Using new toc
[23:56:06] <tissf> Traceback (most recent call last):
[23:56:09] <tissf> File "../docs/src/lyxtree.py", line 729, in ?
[23:56:10] <tissf> doc, outfile = parse(sys.argv[1:])
[23:56:12] <tissf> File "../docs/src/lyxtree.py", line 720, in parse
[23:56:13] <tissf> IndexFixer(d)
[23:56:15] <tissf> File "../docs/src/lyxtree.py", line 642, in IndexFixer
[23:56:16] <tissf> n.setAttribute("lcterm", order(term))
[23:56:18] <tissf> NameError: global name 'term' is not defined
[23:56:17] <tissf> make: *** [objects/gui_axis.xml] Erreur 1
[23:56:49] <jepler> hm I must have screwed it up
[23:57:02] <tissf> compile error on the v2_2_branch
[23:57:03] <tissf> noerror with trunk
[23:57:23] <jepler> update and try again?
[23:57:32] <tissf> ok
[23:57:32] <CIA-18> 03jepler 07v2_2_branch * 10emc2/docs/src/lyxtree.py: I am incompetent today