As promised:

It is not possible to get a good focus with a mobile, but this is the level shifter, not a death bug on my desk

Loving the use of strip-board - you must be a glutton for punishment! 

It takes 2 weeks to wait a for a board ... just to find out you've messed something
I've made a small board for just the chip with caps - the rest is easy to be put even on a strip-bard and this way i could also swap the chips at will and test the differences between them.
Now I am (almost) sure the prototype will work as expected

Well, I was going for the more-integration => less to go wrong side of the KISS principle, seems your version was more successful this time round!

I don't have so steady hands (can be seen from the LS soldering), so a friend have helped with the chips actually.
No, it doesn't have solder mask, but most of the pins are power and they are shorted anyway, so starting from there to hold the chip in place is the way he did it.

Two things. One, you're not allowed in my lab ;-p Two: I get better results with the cgminer fork.

Good luck! And be nice to your RPi's. On the other hand, I think they just announced that 2M RPi's have been sold, so they're not exactly scarce.

-a[g

The beta testing is over long time ago.

Here is another shot of my dev board. Cool thing to note here is that the SPI is being handled by a FTDI MPSSE based USB chip. No microcontoller required! It is kind of messy, but the KNK cgminer fork only required changes to a couple of source files.

Everything seems to work, however I have a couple of questions I hope the other developers on here can answer:

What drives the total hash rate of the BitFury chip? When connected to the RPi the board averages 2.0GH/s long term, which when it is connected to my Mac it averages around 1.6-1.7 GH/s.

The short stats message also differs between the RPi and my Mac version. On the RPi it reports ~180MHz with a target hash rate of 2.1GH/s or so. On the Mac it reports around 140MHz with 1.75 GH/s. I looked at the code that calculates these values, but it hurts my head to look at. Can someone give me a summary? I've also played around with the clock bits, but this doesn't seem to do much.

There also seems to be some timing based voodoo for talking to the chip that is based on sleeping for 100ms between SPI transfers. Can someone explain how this plays into the hash rate and the number of shares found?

Thanks!

-a[g

Thanks KNK! Just the information I need. Given this information I think I need to verify that my OSX-ified process-time and wall-clock time routines are returning good numbers (because of course OS X doesn't have clock_gettime()).

-a[g

Do you have INCLK grounded? I didn't at first but once I did it made a huge difference.

-a[g