there is nothing for git-annex to do to support ASIC hashing
This commit is contained in:
parent
680bd465a7
commit
8fdade6819
1 changed files with 6 additions and 0 deletions
|
@ -8,3 +8,9 @@ I got the idea, because I have two RaspberryPis here:
|
||||||
- another one runs 2 old-ish ASIC miners. They are just barely "profitable" right now, so in a few months they will be obsolete
|
- another one runs 2 old-ish ASIC miners. They are just barely "profitable" right now, so in a few months they will be obsolete
|
||||||
|
|
||||||
Both devices to some kind of `SHA256`. I have a feeling this is either extremely easy or extremely complicated to do… :)
|
Both devices to some kind of `SHA256`. I have a feeling this is either extremely easy or extremely complicated to do… :)
|
||||||
|
|
||||||
|
> git-annex uses binaries such as `sha256sum` for hashing large files (large is
|
||||||
|
> currently hardcoded as bigger than 1MB). If you insert a binary with the same
|
||||||
|
> interface as `sha256sum` into your `$PATH`, git-annex will automatically use
|
||||||
|
> it. If you want to use ASIC hashing even for small files, you need to tweak
|
||||||
|
> `Backend/Hash.hs`. --[[HelmutGrohne]]
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue