Post
Topic
Board Hardware
Re: Kano vs Bitsyncom
by
kano
on 12/02/2013, 09:20:53 UTC
IMHO the best proverb to describe this thread is this:

http://en.wikipedia.org/wiki/Cutting_off_the_nose_to_spite_the_face

No, this thread is about the GPL license requirements of cgminer.
It's not about some random person (you) idea about how that fits in with their thoughts on GPL and hardware.

GitSyncom has stated (for the 3rd time ... this time with a date that either just expired or is yet another week away) that they will release the source.

The issue why I brought this argument up was actually mainly due to the bogus excuse as to why they hadn't yet released it.
They supposedly completed 2 Avalon's on the 20th of Jan that contain the results of all of their different source code.
They have supposedly since then been making 12 Avalon a day (each with binaries made from that source code) and yet the bogus excuse was that they needed to remove something from it before they could release it.
Of course there are 2 issues: 1) They can't do that with cgminer and keep to the required licence 2) If they are referring to the non-cgminer code, then well that just means they've now made and shipped over 200 Avalons that have this so called problematic debugging code that is required to be removed - unless the "12 Avalons a day" was bogus.

I can tell you up front:
The cgminer code will be using the FPGA serial-USB library.
The cgminer code will have modified the scanhash is some manner to acquire ~24 work items at a time (instead of 1) coz the Avalon requires a group of items sent to it at a time ... no big deal ... and it's not ground breaking coz it's not even a queue as per discussion about improving performance.
Neither of those are any sort of advancement on cgminer, the first is something I've been removing from cgminer, the 2nd is something that is being developed properly now for the BFL SC's if they appear soon and use it in an optimal way ... as a queue.
The other changes they may have made in cgminer will not be ground breaking in any manner or form.
i.e. there really is no excuse to not have already released the cgminer code by a company who promotes themselves as Open Source to the Bitcoin community.
The results of that are that if anyone else does get an Avalon (which is still questionable more than 3 weeks after they shipped the first one) they are unable to deal with any cgminer problems themselves - and also an already known memory problem cannot be implemented by anyone who gets an Avalon, until the source code is released, without having to reinvent the code (which would also normally be done if any of the devs actually had the hardware Tongue ... though I'll be the one to help Xiangfu to do that ... if he does get an Avalon)

PS they didn't meet their date they supplied last week of having it this weekend just passed.
My comment a few paragraphs up saying 'a date that either just expired or is yet another week away' was before I checked which weekend he said it would be (on the 8th)
...
Anyhow:
Quote
the source code release is set for this weekend on our project timeline at the moment.
...
Even allowing for being in the wrong country (NewYork USA) and adding a whole extra day delay ... it's still past the weekend and no source on the link on the web site or any of the threads I've checked.
I guess it 'could' be a "give the source only to Jeff" ... but as far as Jeff is concerned he doesn't even want it ... and that smells of a rat somewhere with both Jeff and Avalon.