11:47 <sh4rm4> wolfspra1l, did you know that you can push multiple commits at once ? you dont have to push every single commit you make...

11:47 <sh4rm4> just saying since my github startpage is now entirely cluttered by your fpga-tools work :)

11:49 <sh4rm4> additionally if you dont push immediately you can still rebase stuff, ie. commit1, commit2, commit3 which fixes commit1, so 3 and 1 can be rebased into a single commit

11:49 <sh4rm4> if you already pushed, you can't do this without -f

11:55 <sh4rm4> http://i.imgur.com/LdZ3I.png

11:57 <larsc> but it doesn't make sense to horde commits localy

11:57 <larsc> i mean they are several hous appart

11:59 <sh4rm4> i have a very long passphrase for my ssh key

11:59 <sh4rm4> for this reason alone i let the commits accumulate before i push...

12:00 <sh4rm4> and it's not like anybody's waiting eagerly for your commits to show up :)

12:00 <wolfspra1l> just unfollow

12:00 <wolfspra1l> :-)

12:00 <sh4rm4> :)

12:00 <wolfspra1l> I like to push things out because my hdd is making strange clicking sounds, quite simple

12:01 <larsc> I eargerly await any of wolfspra1l's commits ;)

12:01 <wolfspra1l> then I feel good about every line that is in safety

12:01 <sh4rm4> ugh, i see...

12:01 <wolfspra1l> I tried to reinstall a new fedora on a new hdd, but that failed due whatever new kernel issues, so I couldn't continue to waste time with that and just went back to the hdd that includes the nerve wracking clicking

12:01 <wolfspra1l> actually I like it, creates a sense of urgency

12:02 <wolfspra1l> do not expect my push frequency to go down

12:02 <wolfspra1l> :-)

12:02 <sh4rm4> :P

12:02 <wolfspra1l> unless my hdd breaks and I'm busy with a reinstall for 2 days, or I finally switch to the new one ;-)

12:03 <wolfspra1l> it will slow down soon since my daughter returns

12:03 <wolfspra1l> and I am still dancing around the switch boxes/routing which are quite difficult to understand, not difficult as in moon landing, but difficult as in 'damned, why can't they just publish some papers on how it's wired up..."

12:07 <wolfspra1l> sh4rm4: btw without hard feelings, that's a hilarious comment to make. push frequency too high, clutters my view...

12:07 <wolfspra1l> I'm not in any extreme here, coding a bit with a few pushs a day at most. that's already too much? are we in a senior home?

12:08 <sh4rm4> well, i just wanted to share the point of view of a github follower

12:08 <wolfspra1l> absolutely, thanks for bringing it up

12:08 <larsc> wolfspra1l: how does a switch box work?

12:08 <wolfspra1l> I would have never ever thought anyone cares or notices

12:08 <sh4rm4> i unfollowed other projects for this reason

12:08 <wolfspra1l> it's really the clicking thing here...

12:09 <wolfspra1l> not sure, lots of multiplexers I think, mostly 4:1 or maybe 5:1

12:09 <wolfspra1l> the sets of multiplexers are sort of understand, but there's still stuff missing for me to make sense of the bits

12:09 <wolfspra1l> I think 80% or more of the bits in the bitstream initialize those multiplexers or maybe decoders

12:11 <wolfspra1l> but who knows I am really just scratching the surface and that becomes clearer as I go, which is not bad

12:12 <wolfspra1l> for example - even if I can make sense of all bits and the model, that only covers the digital knowledge of the chip. what remains totally invisible to me is any physical knowledge, wire widths, whatever other physical properties/differences between physical devices

12:12 <wolfspra1l> I'm sure there are a lot of them, and they will remain invisible to me for good, unless I work my way through the chip's physical structure

12:13 <wolfspra1l> that will create a big problem later, as I think you cannot just route every signal over every wire, and group/align them at will. without a deeper understand of the physics a lot of those designs will not work well or at all.

12:13 <wolfspra1l> but I just ignore all that for now

12:14 <wolfspra1l> maybe there is a slim chance we can discover some of that in-situ, i.e. by running analysis designs on the chip itself, measuring, etc.

12:14 <wolfspra1l> one by one...

12:14 <wolfspra1l> a lot more commits hopefully coming :-)

13:33 <wpwrak> the main parameters should be fan in/out and delay

13:33 <wpwrak> once you have a few things working, it should be possible to get some usable estimates for all those things

13:42 <lekernel> wolfspra1l: have you seen fig. 3 of http://www.mn.uio.no/ifi/english/research/projects/cosrecos/publications/paper/fpl10beckhoff.pdf ?

13:43 <lekernel> the paper also gives a lot of info on how to make sense of routing configuration bits

14:37 <wpwrak> nice topic (shorts in fpgas) :)

19:24 <GitHub131> [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/milkymist/migen/commit/4164fb4ac93a77cff1a777a52efe8a728bebec03

19:24 <GitHub131> [migen/master] bus/csr: configurable data width - Sebastien Bourdeauducq