1
0
mirror of https://github.com/GOSTSec/sgminer synced 2025-01-01 18:55:36 +00:00
Commit Graph

174 Commits

Author SHA1 Message Date
James Z.M. Gao
c9ae715019 Compile CPU mining for win32 and win64 2013-04-04 22:59:10 +08:00
Kano
3515b6e2e6 BFL stop 1st init command if no device 2013-02-21 07:35:39 +11:00
Kano
6fb32f7b5d convert sleep(const) to nmsleep() 2013-02-08 02:32:27 +11:00
Kano
7abf30b2c0 distinguish between drv and it's id enum now called drv_id 2013-02-03 22:51:05 +11:00
Kano
d057791915 Capitalise driver long names used in applog messages 2013-02-02 20:14:37 +11:00
Kano
7fbc3770b4 USB move usbdev info that needs to stay around into usbinfo 2013-02-02 20:14:36 +11:00
Kano
8f4340bfeb BFL allow a 2nd init attempt if the 1st reply is unknown 2013-02-02 20:14:35 +11:00
Kano
3f4d9fc5d6 BFL use #defined strings for work replies 2013-02-02 20:14:34 +11:00
Kano
34bcc1c66d USB automatically handle losing the device and report nodev in the API 2013-02-02 20:14:29 +11:00
Kano
f53549a861 BFL minimise first initialisation failure delay since it is common 2013-02-02 20:14:28 +11:00
Kano
f9e04a3c5b device_drv - allow .name to be changed before add_cgpu() 2013-02-02 20:14:23 +11:00
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 2013-02-02 20:14:19 +11:00
Kano
44ec755282 BFL USB correct usb stats id 2013-01-02 22:43:48 +11:00
Kano
b099615246 BFL report USB device numbers for init errors and allow faster 'reinit' 2012-12-31 13:04:53 +11:00
Kano
cbf6c71648 BFL libusb driver 2012-12-31 08:54:02 +11:00
Con Kolivas
86fd23a305 Convert remaining modminer and bfl uses of usleep to nmsleep. 2012-11-18 22:25:28 +11:00
Paul Sheppard
9f74e650b3 Tidy up device error counts 2012-11-04 20:17:43 -08:00
Con Kolivas
2c80e16c85 Fix sign warning on windows build for bitforce. 2012-10-07 18:23:31 +11:00
Con Kolivas
735d77f349 Use strtod not strtol for bitforce temp backup. 2012-10-07 12:59:02 +11:00
Con Kolivas
947a67ea24 Cope with broken drivers returning nonsense values for bitforce temperatures. 2012-10-07 12:52:48 +11:00
Kano
ad7aa2b382 FPGA - allow long or short device names in detect code + style police 2012-09-16 11:42:51 +10:00
Kano
9487ba05cd API/BFL identify a device - currently only BFL to flash the led 2012-09-04 12:52:11 +10:00
Kano
7a2407f15c BFL add throttle count to internal stats + API 2012-09-04 02:26:17 +10:00
Kano
71e2f23f47 BFL: missing device id in log message 2012-09-04 02:10:22 +10:00
Con Kolivas
3b234da43f Merge pull request #302 from luke-jr/bugfix_ftdi_alloca
Bugfix: bitforce: Allocate enough space for FTDI description pointers
2012-08-20 19:49:36 -07:00
Con Kolivas
c3e32274ee Cull all the early queue requests since we request every time work is popped now. 2012-08-18 10:37:05 +10:00
Con Kolivas
2480cf23cc Don't try to get bitforce temperature if we're polling for a result to minimise the chance of interleaved responses. 2012-08-15 10:54:38 +10:00
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."
This reverts commit e29d2d92c9.

As P. Shep points out, this breaks re-enabling of a disabled device.
2012-08-15 10:37:51 +10:00
Con Kolivas
c433f234c5 Increase the timeout on bitforce as per Paul Sheppard's suggestion to account for throttling + work time + excess. 2012-08-15 10:19:16 +10:00
Con Kolivas
e29d2d92c9 Only get bitforce temperature at a time when we have not requested any other responses to minimise risk of interleaved responses. 2012-08-15 09:04:17 +10:00
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. 2012-08-12 10:46:31 +10:00
Con Kolivas
f27bcb8ee5 Going back to e68ecf5eb2 2012-08-12 10:45:59 +10:00
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. 2012-08-12 10:29:34 +10:00
Luke Dashjr
fa3a25f876 Bugfix: bitforce: Allocate enough space for FTDI description pointers
Con's uglify of the FTDI autodetect replaced a standard C99 array with non-standard alloca that needs the developer to specify the size in bytes rather than elements, but he didn't account for pointer size at all
2012-08-10 22:19:17 +00:00
Con Kolivas
0adbcd5d07 Fix windows bitforce build. 2012-08-07 21:21:01 +10:00
Con Kolivas
0a79de9375 Convert the serial autodetect functions to use int instead of char to enumerate devices. 2012-08-07 20:55:55 +10:00
Con Kolivas
9cae9a9d7f Make the serial open timeout for BFL generically 1 second on windows. 2012-08-07 20:49:47 +10:00
Con Kolivas
7dffa07ed9 Deuglify windows autodetect code for BFL. 2012-08-07 20:47:18 +10:00
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. 2012-08-07 20:26:24 +10:00
Con Kolivas
4443895f77 Count likely throttling episodes on bitforce devices as hardware errors. 2012-08-05 17:55:35 +10:00
Con Kolivas
0d6763462b Style cleanups. 2012-08-05 16:15:32 +10:00
Con Kolivas
31b01c8ac5 Author: Luke Dashjr <luke-jr+git@utopios.org>
Date:   Thu Jul 12 16:49:26 2012 +0000

    Use FTD2XX.DLL on Windows to autodetect BitFORCE SHA256 devices
2012-08-05 16:13:53 +10:00
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. 2012-08-03 09:49:14 +10:00
Con Kolivas
7fa794a499 It is not critical getting the temperature response in bitforce so don't mandatorily wait on the mutex lock. 2012-08-03 09:26:43 +10:00
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. 2012-08-03 08:12:05 +10:00
Con Kolivas
efba82fb56 Print the 3 parameters that are passed to applog for a debug line in bitforce.c 2012-08-01 20:39:12 +10:00
Con Kolivas
7f8250132a Clear bitforce buffer on init as previously. 2012-08-01 20:08:37 +10:00
Con Kolivas
7aa809ca24 Revert "Revert "Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement.""
This reverts commit 89e613b943.

Leave the delay between each device initialising.
2012-08-01 19:38:28 +10:00
Con Kolivas
a688951d37 Revert "Remove bitforce_thread_init"
This reverts commit 2dfe0d628e.

Roll back to init'ing bitforce devices at regular intervals. They may reinit more than previously thought.
2012-08-01 19:38:18 +10:00
Con Kolivas
ddcf3d20ca Differentiate between the send return value being a bool and the get return value when managing them in bitforce scanhash. 2012-07-31 22:19:39 +10:00