skunkworks: better now?
alex_joni: I tagged 2.2.6 but now I'm going to be away from the computer for two hours or so
I have it building on dapper and hardy/amd64 at the moment
jepler: I'll build it on hardy/i386 and test if all is ok
will let you know before you come back (hopefully)
just got back actually
hmm.. then it's a bit early :)
was about to reboot into hardy :)
hm I broke the dapper package
[ 123.742581] motmod: Unknown symbol sincos
probably affects hardy as well
.. affects hardy as well
I know in general what to fix
.. RELEASE_2_2_6 tag moved
cvs up -r RELEASE_2_2_6 is enough?
I started from a 2.2.5 checkout
so long as you don't have any modified files
I'll do a cvs diff
but I don't keep stuff in these dirs
hardy/amd64 packages uploading .. dapper/i386 packages building
did you rebuild the release info too?
hardy/i386 building here
hm -- no, I forgot
I'll let the files finish uploading, then do it
ok, I'll update for the whole dir
hmm.. I'm getting lots of messages from dpkg-shlibdeps
were those there before?
dpkg-shlibdeps: warning: debian/emc2/usr/lib/python2.5/site-packages/_tk_seticon.so shouldn't be linked with libm.so.6 (it uses none of its symbols).
yeah that's a new warning that they added between dapper and hardy
hmm.. I don't remember that from 2.2.5
probably getting old :)
I'm sure I saw those warnings before today
let me know when you finished uploading
still going .. slow american internte
(well, dapper is still going but hardy is done)
hello from 'hnc'
hmmm -- when I 'loadrt hostmot2' I don't get any pins or parameters. I have a 5i20 card in this machine...
I get plenty of pins when I loadrt hal_m5i20
I will complain to my vendor if that doesn't work
does it know what cards are on it or something?
I still don't have a grasp of how it works
I thought it did but maybe I'm mistaken
I think you need to specify the firmware it needs to load
and exports pins based on that
I hear there's a hostmot manpage
This driver by itself does nothing, the
boards that actually run the firmware require their own drivers before
anything can happen.
so you need to loadrt hm2_5i20
[ 3392.692595] hm2/hm2_5i20.0: invalid cookie, got 0x00000000, expected 0x55AACAFE
[ 3392.692598] hm2/hm2_5i20.0: FPGA failed to initialize, or unexpected firmware?
[ 3392.692602] hm2_5i20.0: board fails HM2 registration
yeah but then I get this ..
did you load a firmware?
If no "firmware=F" string is specified, the FPGA
will not be programmed, and had better have a valid con‐
which firmware do I want?
a typical value for F might be
whee that did it
I wonder if it works
cradek: transfer done, can you sign the dapper repository?
jepler: seems the manpage is usefull after all
OK .. well I think 2.2.6 works, and all the files I need to upload are in place
I'll come back in a bit to send the announce and work on the wiki
I only started uploading the files
after that is finished, I'll rebuild the release and sign the hardy repo
wonder if this will be the last 2.2 release.
cradek: I doubt that
at least 2.3 feels pretty far to me
yeah, me too.
it has feature-creep
what is feature-creep?
where you never stop adding things, so it never stabilizes
(we can fit just one more new feature in this release!)
yay for matrox video cards
14982 jitter, working direct rendering
hardy repo updated and signed
what great timing - thanks, guys.
cradek: you on hardy?
yes the hnc is running hardy
next step is to mount the mesa boards, then wire them up, then spend a month writing ladders
yep I'm at the interesting part...
thanks again for the release
yeah, thanks jeff
aww shucks it weren't nothin'
time for a copyright date update in AXIS...
(has it been that many years??)
whee.. sf is really orange
speaking of SF, its "project news" tab needs an entry for 2.2.6
* jmkasunich tries to figure out how to do that
* jmkasunich gives up
BigJohnT_ is now known as BigJohnT
nothing terrible spotted in 2.2.6 yet? what a relief.
uh-oh, I'm baffled by the hm2 stuff
I went through that earlier too
I ended up with this in my hal file:
loadrt hostmot2 debug_idrom=1
loadrt hm2_5i20 config=firmware=hm2/5i20/SVST8_4.BIT
I still haven't used it for anything, but it does have plausible-looking pins and parameters
if the manpage is up to date, it says encoders don't have index yet. I think that means I'll need to use the old one for now...
I think that's true; I don't see any 'index-enable' pins.
the old one gives me 4 dacs, 8 (?) encoders, 32 ins, 16 outs
looks like a good match - maybe I just have to plug in the three boards in the right places and it will work.
huh -- I wonder if the "index mask" on connector P4 works
on the one hand it might be useful for you
on the other hand when using that port as gpio it seems like it would create spurious behavior of the index pulses
oh, I see, you program a register to do it
looks like P2 is the servo card, P3/P4 are the IO cards
yes I am pretty sure that's true
crap, SF release process is really shitty
they changed the upload ftp server (which doesn't work atm)
jepler: did you fix this? http://sourceforge.net/tracker/index.php?func=detail&aid=1938763&group_id=6744&atid=106744
alex_joni: I'm not sure
BigJohnT: I notice that the documentation for 2.2 now refers to G38.3 .4 and .5, but these are not in 2.2 (only in TRUNK)
BigJohnT: is it possible that you accidentally moved this back into 2.2 when making other modifications?
hm, no -- it was put there by tissf, probably a mistake
BigJohnT: so you're off the hook :-P