Quote from: Luke-Jr on February 04, 2014, 05:14:39 PM

Quote from: Askit2 on February 04, 2014, 11:12:28 AM

Lets be honest. bfgminer wasn't mining on anything in the early days of FPGA's. It didn't exist.

Yes it did, it was released under the name "cgminer", in collaboration with Con/Kano's GPU miner.

By releasing cgminer with your code it doesn't change the fact bfgminer was not in existence as bfgminer. Cgminer existed but bfgminer wasn't a thing yet. Let me give an example to provide some illuminated cognition. There was a car made by Pontiac called the LeMans. It existed for a few years before its more famous option package was available. Now did the parts of the GTO exists in a GM catalogue? Most of them. Does that mean anyone owned a 60 GTO? No. The product in question didn't exist as such until it did. It doesn't matter that something like it existed. What I am saying is that until you released your miner that your miner by its name and only cgminer pulls and teams work existed. You have added people since and that's great. That doesn't change the fact that only one miner was released.

Quote from: Luke-Jr on February 04, 2014, 05:14:39 PM

Quote from: Askit2 on February 04, 2014, 11:12:28 AM

After BFL singles support and some Icarus related windows issues you went your own way.

No, after ASICs were announced, Con/Kano went their own way because they were upset.

no the split happened when ztex boards released the Y version. Cgminer supported it bfgminer either did or was working on it. Now april of 2012 wasn't when ASICs started. They where announced before July of 2012. I am pretty sure it was in June. Even then it isn't like everything was done with FPGA's.

Quote from: Luke-Jr on February 04, 2014, 05:14:39 PM

Quote from: Askit2 on February 04, 2014, 11:12:28 AM

Now maybe you wrote a lot of code in cgminer I personally don't know. The commits would know. That having been said you hadn't re-written the entire code base just for FPGA's. You made use of everything cgminer did for GPU's and potentially added on some interfacing code to allow non GPU devices.

No, cgminer had been very tied around GPU code, and had entirely independent code for CPUs.
It took some pretty big changes to make it into a modular/driver based model.

I am not saying it didn't. What I was saying is that based on commits at the time you didn't single handedly change it.

Quote from: Luke-Jr on February 04, 2014, 05:14:39 PM

Quote from: Askit2 on February 04, 2014, 11:12:28 AM

Now that doesn't mean big freaking deal miner existed. It means cgminer supported the items that where supported up until you left by whatever developer maintained the devices. The fact that your software pulled 2.3.4 to start means 2.3.3 and before versions of cgminer worked just fine without bfgminer existing.

You have an awfully centralised way of looking at things. Just because early versions of BFGMiner were released in this thread, thanks to my efforts to try to collaborate rather than release independently at the start, somehow means in your mind that everything only "counts" toward Con/Kano's sole credit after they decide to split off?

Not centralized way of looking at anything (ignoring your typo). There was a project named cgminer. It existed yours as bfgminer didn't. Now did some code live in cgminer that you created sure. I never argued against that. But you didn't have bfgminer released until far later. The credit as such goes not to just you but the whole team that worked on cgminer at the time. Yes con and kano and lJr get credit in my mind. That being said the split off is where bfgminer started. Sorry if I forgot anyone who did provide code I don't mean to leave you out of credit. Just trying to make a point.