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

187 Commits (ec881c41a4bcb1512d2683032ecc7c4cb5bcbdc9)

Author SHA1 Message Date
Con Kolivas e52762c57a There is no point zeroing temperature in BFL if we fail to get a response, and we should register it as a HW error, suggesting throttling.
12 years ago
Con Kolivas 4443895f77 Count likely throttling episodes on bitforce devices as hardware errors.
12 years ago
Con Kolivas 0d6763462b Style cleanups.
12 years ago
Con Kolivas 31b01c8ac5 Author: Luke Dashjr <luke-jr+git@utopios.org>
12 years ago
Con Kolivas 245552c5b5 Clear the bitforce buffer whenever we get an unexpected result as it has likely throttled and we are getting cached responses out of order, and use the temperature monitoring as a kind of watchdog to flush unexpected results.
12 years ago
Con Kolivas 7fa794a499 It is not critical getting the temperature response in bitforce so don't mandatorily wait on the mutex lock.
12 years ago
Con Kolivas 5118e3ee7c Check there is a cutoff temp actually set in bitforce before using it as a cut off value otherwise it may think it's set to zero degrees.
12 years ago
Con Kolivas efba82fb56 Print the 3 parameters that are passed to applog for a debug line in bitforce.c
12 years ago
Con Kolivas 7f8250132a Clear bitforce buffer on init as previously.
12 years ago
Con Kolivas 7aa809ca24 Revert "Revert "Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement.""
12 years ago
Con Kolivas a688951d37 Revert "Remove bitforce_thread_init"
12 years ago
Con Kolivas ddcf3d20ca Differentiate between the send return value being a bool and the get return value when managing them in bitforce scanhash.
12 years ago
ckolivas 23a8c60420 Revert "bitforce: Skip out of sending work if work restart requested"
12 years ago
Luke Dashjr cf36331d81 bitforce: Skip out of sending work if work restart requested
12 years ago
Kano c55830502a BFL force all code to timeout to avoid hanging
12 years ago
Luke Dashjr b347a178f6 bitforce: Use "full work" vs "nonce range" for kernel name
12 years ago
Con Kolivas b6a23d0027 bitforce_get_result returns -1 on error now.
12 years ago
Con Kolivas aa723e7102 Check return value of read in BFgets
12 years ago
Luke Dashjr 68111323b3 Bugfix: Make our Windows nanosleep/sleep replacements standards-compliant (which fixes nmsleep) and include compat.h for bitforce (for sleep)
12 years ago
Con Kolivas ac55cec60b Fix whitespace mangling.
12 years ago
Con Kolivas 89e613b943 Revert "Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement."
12 years ago
Paul Sheppard d4d5b28e5f Abbrv. correction
12 years ago
Paul Sheppard c37a3f3007 Put kname change for broken nonce-range back in
12 years ago
Paul Sheppard 2c54522d7d Add average wait time to api stats
12 years ago
Paul Sheppard 01a69ee45e Revert "Merge branch 'ave_time' of https://github.com/pshep/cgminer.git"
12 years ago
ckolivas 0785886b53 Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement.
12 years ago
ckolivas 9eaac43982 Spelling typo.
12 years ago
ckolivas 5c7e03084a Modify te scanhash API to use an int64_t and return -1 on error, allowing zero to be a valid return value.
12 years ago
Paul Sheppard 4dc1bf2319 Missed one nonce-range disabling.
12 years ago
Paul Sheppard 3cc0aa76ad Add average return time to api stats
12 years ago
Paul Sheppard 2dfe0d628e Remove bitforce_thread_init
12 years ago
Paul Sheppard 953ecd9e6a Change timeouts to time-vals for accuracy.
12 years ago
Paul Sheppard 19b4d2b9de More BFL tweaks.
12 years ago
Con Kolivas 957d196180 Make long timeout 10seconds on bitforce for when usleep or nanosleep just can't be accurate...
12 years ago
Con Kolivas 57e38d059e Make disabling BFL nonce range support a warning since it has to be explicitly enabled on the command line now.
12 years ago
Con Kolivas fd55fab96a Make bitforce nonce range support a command line option --bfl-range since enabling it decrease hashrate by 1%.
12 years ago
Con Kolivas b8484956e6 Add sanity checking to make sure we don't make sleep_ms less than 0 in bitforce.
12 years ago
Luke Dashjr d4af2d0535 Turn work_restart array into a bool in thr_info
12 years ago
Con Kolivas e97adc91c3 The fastest minirig devices need a significantly smaller starting sleep time.
12 years ago
Con Kolivas 74b96d4b3f Use a much shorter initial sleep time to account for faster devices and nonce range working, and increase it if nonce range fails to work.
12 years ago
Con Kolivas 13cf568961 Use nmsleep instead of usleep in bitforce.
12 years ago
Con Kolivas 390d77a202 Add more comments explaining how sleep time equals wait time and simplify the
12 years ago
Con Kolivas 69a11508a4 delay_time_ms is always set so need not be initialised in bitforce.
12 years ago
Con Kolivas 9e8726b109 Increase bitforce timeout to 10 seconds.
12 years ago
Con Kolivas a3faf63c96 Add more hysteresis and poll ~5 times to allow for timer delays in bitforce devices.
12 years ago
Con Kolivas afc6ae58a5 Change message about broken nonce range support to verbose level instead of debug.
12 years ago
Con Kolivas 86ba7d79df Display the actual duration of wait when it is greater than the cutoff.
12 years ago
Con Kolivas 5a096c1c13 Set nonce to maximum once we determine nonce range support is broken.
12 years ago
Con Kolivas 88dd599f34 Initial wait time is always known so no need to zero it beforehand in bitforce.
12 years ago
Con Kolivas 1b0a0ac5db No point counting wait time until the work is actually sent to bitforce devices.
12 years ago