 Con Kolivas
|
07fca3e289
The bitforce buffer is cleared and hw error count incremented on return from a failed send_work already so no need to do it within the send_work function.
|
13 years ago |
|
Con Kolivas
|
f27bcb8ee5
Going back to e68ecf5eb275e1cc2dc22c7db35b0bd8d9c799de
|
13 years ago |
|
Con Kolivas
|
65f4e2af3e
The bitforce buffer is cleared and hw error count incremented on return from a failed send_work already so no need to do it within the send_work function.
|
13 years ago |
|
Con Kolivas
|
0adbcd5d07
Fix windows bitforce build.
|
13 years ago |
|
Con Kolivas
|
0a79de9375
Convert the serial autodetect functions to use int instead of char to enumerate devices.
|
13 years ago |
|
Con Kolivas
|
9cae9a9d7f
Make the serial open timeout for BFL generically 1 second on windows.
|
13 years ago |
|
Con Kolivas
|
7dffa07ed9
Deuglify windows autodetect code for BFL.
|
13 years ago |
|
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.
|
13 years ago |
|
Con Kolivas
|
4443895f77
Count likely throttling episodes on bitforce devices as hardware errors.
|
13 years ago |
|
Con Kolivas
|
0d6763462b
Style cleanups.
|
13 years ago |
|
Con Kolivas
|
31b01c8ac5
Author: Luke Dashjr <luke-jr+git@utopios.org>
|
13 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.
|
13 years ago |
|
Con Kolivas
|
7fa794a499
It is not critical getting the temperature response in bitforce so don't mandatorily wait on the mutex lock.
|
13 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.
|
13 years ago |
|
Con Kolivas
|
efba82fb56
Print the 3 parameters that are passed to applog for a debug line in bitforce.c
|
13 years ago |
|
Con Kolivas
|
7f8250132a
Clear bitforce buffer on init as previously.
|
13 years ago |
|
Con Kolivas
|
7aa809ca24
Revert "Revert "Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement.""
|
13 years ago |
|
Con Kolivas
|
a688951d37
Revert "Remove bitforce_thread_init"
|
13 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.
|
13 years ago |
|
ckolivas
|
23a8c60420
Revert "bitforce: Skip out of sending work if work restart requested"
|
13 years ago |
|
Con Kolivas
|
2fb95c0057
Merge pull request #276 from luke-jr/bf_send_restart
|
13 years ago |
|
Con Kolivas
|
150b29d445
Merge pull request #268 from luke-jr/bf_generic_kname
|
13 years ago |
 Luke Dashjr
|
cf36331d81
bitforce: Skip out of sending work if work restart requested
|
13 years ago |
 Kano
|
c55830502a
BFL force all code to timeout to avoid hanging
|
13 years ago |
|
Luke Dashjr
|
b347a178f6
bitforce: Use "full work" vs "nonce range" for kernel name
|
13 years ago |
|
Con Kolivas
|
b6a23d0027
bitforce_get_result returns -1 on error now.
|
13 years ago |
|
Con Kolivas
|
761bd77288
Merge pull request #267 from luke-jr/bugfix_winsleep
|
13 years ago |
|
Con Kolivas
|
aa723e7102
Check return value of read in BFgets
|
13 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)
|
13 years ago |
|
Con Kolivas
|
ac55cec60b
Fix whitespace mangling.
|
13 years ago |
