Browse Source

Update ASIC-README for bitfury devices.

Con Kolivas 12 years ago
parent
commit
3139a6c7d2
1 changed files with 16 additions and 5 deletions
  1. 16 5
      ASIC-README

+ 16 - 5
ASIC-README

@@ -1,10 +1,10 @@
 SUPPORTED DEVICES
 SUPPORTED DEVICES
 
 
 Currently supported devices include the Avalon (including BitBurner), the
 Currently supported devices include the Avalon (including BitBurner), the
-Butterfly Labs SC range of devices and the ASICMINER block erupters. No COM
-ports on windows or TTY devices will be used by cgminer as it communicates
-directly with them via USB so it is normal for them to not exist or be
-disconnected when cgminer is running.
+Butterfly Labs SC range of devices, the ASICMINER block erupters and the BPMC
+BF1 (bitfury) USB devices. No COM ports on windows or TTY devices will be used
+by cgminer as it communicates directly with them via USB so it is normal for
+them to not exist or be disconnected when cgminer is running.
 
 
 
 
 The BFL devices should come up as one of the following:
 The BFL devices should come up as one of the following:
@@ -24,7 +24,18 @@ ASICMINER block erupters will come up as AMU.
 
 
 ASICMINER devices need the --enable-icarus option when compiling cgminer.
 ASICMINER devices need the --enable-icarus option when compiling cgminer.
 Also note that the AMU is managed by the Icarus driver which is detailed
 Also note that the AMU is managed by the Icarus driver which is detailed
-in the FPGA-README
+in the FPGA-README. Configuring them uses the same mechanism as outlined
+below for getting started with butterfly labs ASICs.
+
+
+BITFURY devices
+
+Bitfury devices need the --enable-bitfury option when compiling cgminer.
+
+Currently only the BPMC BF1 devices AKA redfury/bluefury are supported and
+come up as BF1. There are no options available for them. Bitfury device are
+also set up as per the butterfly labs ASICs below.
+
 
 
 
 
 GETTING STARTED WITH BUTTERFLY LABS ASICS
 GETTING STARTED WITH BUTTERFLY LABS ASICS