[Pkg-bitcoin-devel] bfgminer package

[Scott Howard]

Sorry for the extra email, Martin - i just saw I didn't reply to the list
On Wed, May 1, 2013 at 3:13 PM, Martin Str|mberg <ams at ludd.ltu.se> wrote:
> Scott Howard said:
>> would work better for their needs, like Dmitry said. For example,
>> cgminer dropped all cpumining code but bfgminer still has it; bfgminer
>> supports GBT (I don't think cgminer does); each has their own drivers
>
> Well I recently compiled cgminer (I don't remember exactly which
> version but I think it was 2.11.<something>) and it did support
> cpumining. Not that you would use that unless you had free
> electricity or too much money.

As of version 3, it's gone:
https://github.com/ckolivas/cgminer/commit/f4b27907613b783716482428c3349fada46071e5

> As for GBT, isn't stratum that is the way to go?

Stratum has more support via mining pools (and is what I choose to use
on my personal p2pool node). I'm just listing differences between the
two, not the merits of those differences.

> Luke-Jr said:
>> the free Mesa/LLVM drivers (cgminer requires non-free fglrx).
>
> cgminer doesn't require flgrx as I managed to compile it with/for
> nvidia as well. But that is also non-free, of course.
>
>
> Speaking of non-free, as cgminer (with GPU support) requires non-free
> AMD or Nvidia drivers, does that make cgminer go into non-free or
> contrib or what?

You don't need AMD or Nvidia drivers since you don't need a GPU to run
cgminer. USB devices (FPGAs) and cpus are supported even if you don't
have non-free enabled. Now Avalons and BFL SCs are supported too, you
can run cgminer on a raspberry pi using entirely main sources.

> In another mail, Luke-Jr said:
>> There are also many pools, including ones which are not detrimental to the
>> Bitcoin network (as Ozcoin is), which recommend BFGMiner.
>
> In what way is Ozcoin detrimental? I have it as a backup pool, so I
> want to know why I should I remove it?

not sure about this, never interacted with them