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

171 Commits (983fe2b0c0e0c0365dc457cc1d40ef7025bbb53f)

Author SHA1 Message Date
Kano 7abf30b2c0 distinguish between drv and it's id enum now called drv_id
12 years ago
Kano d057791915 Capitalise driver long names used in applog messages
12 years ago
Kano 7fbc3770b4 USB move usbdev info that needs to stay around into usbinfo
12 years ago
Kano 8f4340bfeb BFL allow a 2nd init attempt if the 1st reply is unknown
12 years ago
Kano 3f4d9fc5d6 BFL use #defined strings for work replies
12 years ago
Kano 34bcc1c66d USB automatically handle losing the device and report nodev in the API
12 years ago
Kano f53549a861 BFL minimise first initialisation failure delay since it is common
12 years ago
Kano f9e04a3c5b device_drv - allow .name to be changed before add_cgpu()
12 years ago
Kano a344deb6ac rename device_api -> device_drv and all related api -> drv and add a device_drv->drv enum for identifying which driver each is
12 years ago
Kano 44ec755282 BFL USB correct usb stats id
12 years ago
Kano b099615246 BFL report USB device numbers for init errors and allow faster 'reinit'
12 years ago
Kano cbf6c71648 BFL libusb driver
12 years ago
Con Kolivas 86fd23a305 Convert remaining modminer and bfl uses of usleep to nmsleep.
12 years ago
Paul Sheppard 9f74e650b3 Tidy up device error counts
12 years ago
Con Kolivas 2c80e16c85 Fix sign warning on windows build for bitforce.
12 years ago
Con Kolivas 735d77f349 Use strtod not strtol for bitforce temp backup.
12 years ago
Con Kolivas 947a67ea24 Cope with broken drivers returning nonsense values for bitforce temperatures.
12 years ago
Kano ad7aa2b382 FPGA - allow long or short device names in detect code + style police
12 years ago
Kano 9487ba05cd API/BFL identify a device - currently only BFL to flash the led
12 years ago
Kano 7a2407f15c BFL add throttle count to internal stats + API
12 years ago
Kano 71e2f23f47 BFL: missing device id in log message
12 years ago
Con Kolivas c3e32274ee Cull all the early queue requests since we request every time work is popped now.
13 years ago
Con Kolivas 2480cf23cc Don't try to get bitforce temperature if we're polling for a result to minimise the chance of interleaved responses.
13 years ago
Con Kolivas 83675099b9 Revert "Only get bitforce temperature at a time when we have not requested any other responses to minimise risk of interleaved responses."
13 years ago
Con Kolivas c433f234c5 Increase the timeout on bitforce as per Paul Sheppard's suggestion to account for throttling + work time + excess.
13 years ago
Con Kolivas e29d2d92c9 Only get bitforce temperature at a time when we have not requested any other responses to minimise risk of interleaved responses.
13 years ago
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 e68ecf5eb2
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
Luke Dashjr fa3a25f876 Bugfix: bitforce: Allocate enough space for FTDI description pointers
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
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