Quote from: spegelius on February 08, 2014, 10:45:41 AM

Quote from: kano on February 07, 2014, 02:54:49 AM

Quote from: spegelius on February 05, 2014, 07:08:55 PM

...
Just to confirm, this doesn't support Bitfury v1.2 hcards/mcard combo? Compiled with --enable-bitfury and it doesn't find anything. And no mention in ASIC-README about hcards...

--enable-bab

Bitfury never supported my writing the software and wouldn't even sell me hardware - so it wasn't until someone sent me a BlackArrowBitfury board that I could write and test a driver for it.

The detection code and work send command is almost the same logic as chainminer - just less bugs Tongue

If they've updated the code and not released (i.e. don't want anyone to support their hardware) then yeah my code won't know about the updates
https://github.com/bfsb/chainminer is their code as far as I know ...

Thanks, got it working, doing quite nice, only 10-15GH/s slower than what Bifury's management page says when mining with chainminer. With chainminer i have handtuned the chip speeds. 248GH/s on average (10 hours of runtime) versus 260 - 267 in chainminer. I wonder if manual tuning of those autotune parameters would bring it up.

I'll let this run for a while.

The --bab-options will allow it to go higher also.
Mainly the first parameter, the Max speed - it defaults to 55 but will allow up to 57
(but that depends on if your board can handle it that high also)

I set the defaults to match a 'slower' BitFury board so that people who tried it didn't blow anything up without messing with options

I've not actually been able to run it on my 6 board for a while now - so I don't know how well it goes with a lot more boards
(the 6 board setup has been out of my hands for a couple of weeks now)
It may still require some tuning (of the 'Delay' code to get the average down when there are a lot of boards) but until I have a larger board setup to test with, I can't really sort that one out.
Shouldn't be too much longer.

It checks each chip results roughly every 5minutes and then tunes them up or down based on HW% for that 5 min of data.
default is down if >10% HW and up if <1%

I do still have other ideas for tuning (and dealing with dead chips coz they use double or more CPU than a live chip)