 Luke Dashjr
|
8cfb0dc7c5
Merge branch 'bf_thrttl_nores' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
ea6abe58f9
Bugfix: bitforce: Don't count hashes that never happened due to throttling
|
13 years ago |
|
Luke Dashjr
|
bfbe7cee1f
Merge branch 'bugfix_bf_timeout' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
d4f755d3d1
Bugfix: Deal with serial_open timeout maximum (25.5s)
|
13 years ago |
|
Luke Dashjr
|
7594c7ea7b
Merge branch 'bugfix_bf_gblnum' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
6f11522b53
Bugfix: bitforce: Include the correct device id in "garbled response" warning
|
13 years ago |
|
Luke Dashjr
|
3faff788ce
Merge commit '0adbcd5' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
ed4d6c4be0
Merge commit '0a79de9' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
4c34b7fadf
Merge commit '7dffa07' into bfgminer
|
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 |
|
Luke Dashjr
|
7123bdc5cf
Merge branch 'bf_err_reopen' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
65eccd3b77
bitforce: Reopen on communication error
|
13 years ago |
|
Luke Dashjr
|
d9d0ff1412
Merge commit '4443895' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
37400e6830
Merge branch 'bugfix_bf_timeout' into bfgminer
|
13 years ago |
|
Luke Dashjr
|
07b6133bdd
Bugfix: bitforce: Increase serial read timeout to 30 seconds during actual mining, to tolerate more throttling
|
13 years ago |
|
Luke Dashjr
|
7f849ad503
Merge commit '0d67634' into bfgminer
|
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 |
|
Luke Dashjr
|
76fe0fada3
Merge commit '245552c' into bfgminer
|
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 |
|
Luke Dashjr
|
27bda917d6
Merge commit 'efba82f' into bfgminer
|
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 |
