GOSTSec
/
sgminer
mirror of https://github.com/GOSTSec/sgminer
1
0
Fork 0
Code Issues Releases Wiki Activity
2741 Commits
12 Branches
10 Tags
44 MiB
Tree: 127b638263
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '127b638263'
${ noResults }
Commit Graph

5 Commits (127b638263e7a8d05270e14e2b010406e10528c5)

Author SHA1 Message Date
Con Kolivas e49bd98196 Use the scrypt CPU code to confirm results from OCL code, and mark failures as HW errors, making it easier to tune scrypt parameters.
12 years ago
Con Kolivas b9e5f8e550 Revert "Use cpu scrypt code to check if an scrypt share is below target before submitting it."
13 years ago
Con Kolivas 808f403a14 Use cpu scrypt code to check if an scrypt share is below target before submitting it.
13 years ago
Con Kolivas 54f1b80824 Free the scratchbuf memory allocated in scrypt and don't check if CPUs are sick since they can't be. Prepare for khash hash rates in display.
13 years ago
Con Kolivas a5ebb71216 Add cpumining capability for scrypt.
13 years ago