 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
|
13 years ago |
|
Kano
|
44ec755282
BFL USB correct usb stats id
|
13 years ago |
|
Kano
|
b099615246
BFL report USB device numbers for init errors and allow faster 'reinit'
|
13 years ago |
|
Kano
|
cbf6c71648
BFL libusb driver
|
13 years ago |
 Con Kolivas
|
86fd23a305
Convert remaining modminer and bfl uses of usleep to nmsleep.
|
13 years ago |
 Paul Sheppard
|
9f74e650b3
Tidy up device error counts
|
13 years ago |
|
Con Kolivas
|
2c80e16c85
Fix sign warning on windows build for bitforce.
|
13 years ago |
|
Con Kolivas
|
735d77f349
Use strtod not strtol for bitforce temp backup.
|
13 years ago |
|
Con Kolivas
|
947a67ea24
Cope with broken drivers returning nonsense values for bitforce temperatures.
|
13 years ago |
|
Kano
|
ad7aa2b382
FPGA - allow long or short device names in detect code + style police
|
13 years ago |
|
Kano
|
9487ba05cd
API/BFL identify a device - currently only BFL to flash the led
|
13 years ago |
|
Kano
|
7a2407f15c
BFL add throttle count to internal stats + API
|
13 years ago |
|
Kano
|
71e2f23f47
BFL: missing device id in log message
|
13 years ago |
|
Con Kolivas
|
3b234da43f
Merge pull request #302 from luke-jr/bugfix_ftdi_alloca
|
13 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 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 |
 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 |
