Quote from: PatMan on May 30, 2014, 01:39:20 PM

Quote from: kano on May 28, 2014, 02:45:51 AM

Bitmain does some terrible things in their driver including ... discarding stale work in the driver before passing it to the work validation code.
This means on p2pool that if you find a stale block that is still a valid network block, it will be discarded. Oh well.

Use my driver for S1 if you don't want to throw such valid blocks away on p2pool.

My S2 driver is still in development - I'm still trying to work out why the device thinks it's a good idea to have >8000 work items queued in it - more than 30s of work - and to work out how to reduce that without letting it get idle - so I'm still waiting on source code from bitmain.

Hey Kano - did Bitmain get back to you yet my man?

My poor S2's are crying out to be set free......... Cheesy

Peace.

No more source yet.
I have everything except the SPI kernel code (which I'll implement in cgminer if I can get it - and solve it all in one place)
Code, of course, is necessary since there are no Bitmain docs on the AntMiner hardware.

Bitmain US has been ever so helpful with my S2 though

Replacement boards and controllers after that pile of damage that originally arrived.

It's rather annoying though that mine doesn't work 100%, since I'm really not sure how my current replacement driver performs.
I can get it running at >990GH/s for hours, but then find it drops. At least I do also get the same issue with their version of the driver ... so it must be my S2 - but I simply cant be 100% certain if it is hardware, the SPI kernel module, or the driver.
I'll probably put out a test firmware next week anyway - with the new cgminer and also a small collection of changes here and there in the firmware itself - so I can see some comparisons on various S2s.

Running yet another overnight run to see how it goes ... after a few hours.
This time it's a new backplane AND a new controller ... fingers crossed.
(I'm 99% sure the 10 boards are OK since I can swap them around without effect)