AFAIK oclHashcat is closed source.
It is more like Intel is a huge company and different departments have different allegiances.
Though I guess it makes sense to send a message that doing good doesn't necessarily mean undoing your evil.
AFAIK oclHashcat is closed source.
Go look at the top contributors list to the Linux kernel sometime, you'll note that Intel consistently the largest contributing company that isn't a 100% Linux based organization like Redhat. You won't see AMD anywhere near the top of that list. I think that the fact that Intel is the first company to bring Android into the 64-bit world and that there are excellent Chromebooks running on Haswell parts speaks volumes about how important they think Linux is and where they are going with Linux.
Just remember that back in the 90's when Microsoft was on trial for anti-trust violations it was Jerry Sanders, CEO of AMD, who got up on the witness stand and testified in favor of Microsoft. I always remember that when their PR department starts up with the usual self-serving whining about how Intel is a "monopoly" or something.
Just remember that AMD branded its own CPUs as "Athlon XP" right around 2001 when Microsoft launched "Windows XP". You think that was a coincidence?
When thinking about Intel vs. AMD here's the easiest way to frame the question: "Would my machine even boot if I stripped out all the Linux code contributed by company X". If you strip out AMD's contributions, then even on an AMD box your machine would still boot fine (you might lose GPU drivers if you use open-source AMD drivers). If you strip out all the Intel-contributed code, your AMD box wouldn't even come close to completing a boot sequence.
I'd actually be curious to know what the ATI firmware has access to. Since the firmware is only used for 3D functions (xf86-video-ati is 100% open source, afaik) does that mean that the firmware only has access to 3D-related things? Additionally I seem to recall an ATI dev posting here on the forums in a post a few months ago explaining that while the firmware code is proprietary, the firmware operation is very transparent and it's supposedly pretty clear to see what's going on with it.What if they have backdoors in the Firmware too?
I'm not sure that RadeonHD was any different -- as mentioned above, I'm pretty sure all Radeon cards have required a pretty minimal firmware blob only for 3D functions. This is how distros like Trisquel get away with running on ATI systems -- they just use the 2D driver, and don't touch the 3D stuff because it's the 3D firmware that's proprietary, not the 2D.If you remember, AMD pushed *hard* to use a firmware blob in Radeon, instead of the clean-room approach of RadeonHD.
I'm still leaning toward "debugging function" as an explanation. Though really, in my mind, what this comes down to is the fact that Nvidia is just far more intelligent about their variable/function naming. :P
It's interesting how people blow stuff out of proportion without facts, but lets see what AMD's PR can come up with.
An AMD dev on here said a while back the firmware only ran during card initialization and was mainly to obfuscate how it starts up. Doesn't really excuse it existing, I wonder why nobody has tried to just use their card documentation to just rewrite the firmware blobs.Additionally I seem to recall an ATI dev posting here on the forums in a post a few months ago explaining that while the firmware code is proprietary, the firmware operation is very transparent and it's supposedly pretty clear to see what's going on with it.
TestBackdoor lol ... I tried this on my girlfriend once. I think they're implying that they are putting it in our... oh wait.
Yeah, keep bashing AMD and use your NSA enabled Intel CPU's you fuckwits. Okay lets see if this damn thing exists.... osTestBackdoorATI, yup it's there. I guess be thankful it's only a test .... Oh well, It's not like facebook, google, apple, microsoft or another company is holding out. I would bet if this is what it seems NVidia kowtowed as well. Hopefully for their PR they didn't name their backdoor... um backdoor..