Quote from: dogie on October 15, 2014, 03:43:28 PM

Quote from: MrTeal on October 15, 2014, 03:38:27 PM

Quote from: dogie on October 15, 2014, 03:28:39 PM

But he did say:

Quote

They just need to get off their arses and fix their driver which appears broken.

Yeah, he did. Not sure what you're disagreeing with, the issue isn't resolved at this point and is contingent on Bitmain fixing their driver.

Alternately, when you talk to them you should bring up the possibility of open sourcing their chip protocol and driver source. It would solve a lot of their problems.

Just disagreeing with the people saying it can't be fixed with firmware. Open sourcing is a decision which someone higher would have to do.

Well, that it can be fixed with firmware remains to be seen, but hopefully it doesn't drag on too long. I would be surprised if they can't optimize it to the point where it can be made to work, but it's unfortunate that they went with the controller they did and didn't get this issue sorted out before release. It's really a little surprising since a stock BBB should have more than enough muscle to push through the shares, unless something else on the board is bottlenecking things.

Really, both sides of this debate are getting a little ridiculous. For your part dogie, you seem very quick to jump on anyone suggesting that there is a hardware issue which only exacerbates the problem now that you're a paid rep for the company. I'm having a hard time faulting you for being a little defensive given the vitriolic attacks against you that are unrelated to the issues at hand, but not everyone that comments on these posts is attacking you or Bitmain. People just want to see the problem resolved.