Quote from: ckolivas on March 30, 2014, 10:03:14 PM

Quote from: cscape on March 23, 2014, 04:04:46 PM

The protocol is exactly the same as for the bi*fury devices (and also the same for the One String Miner), so cgminer already supports them.

The code assumes 2 job queues so I assume you worked within that framework despite the extra chips?

Not sure where the 2 job queues come from, but the firmware internally uses a single queue with room for 4 jobs. That's the same on bi-fury and hex-fury. The only difference is that the hex-fury jobs are processed faster because there are more chips, but this should be transparent for the driver.

For the OneStringMiner version with the serial bus, the job queue has been extended to 16 (but we're still experimenting with that), because it supports a total of 16 boards with 15 chips each, so it goes through the work a lot faster.

cscape

Posts

Merits