Seem unreasonable to me. Even without a legal protection there is some degree of protection for the original creator something as complicated as a CPU.
It's a poison pill which means Intel themselves would be the only serious buyer.
[1] https://www.trustedreviews.com/news/amd-reveals-its-ready-to...
Which market regulators would never allow. This is even bigger in terms of monopoly than Nvidia trying to buy arm.
Yes. There's no requirement to sell licenses to patents in general. Sometimes (not always) if a patent is included by a government in a standard that government will require the owning company to license it on "Fair, Reasonable, And Non-Discriminatory" terms (FRAND). Most patents, including the x86, x86_64, and various extension patents are not required to be licensed under FRAND terms.
AMD and Intel have a mutual licensing agreement. When Intel patents a new extension, they license it to AMD. Likewise when AMD patents a new extension, the license it to Intel. That's why Intel CPUs use the AMD x86_64 instruction set, AMD CPUs use the Intel AVX 512 vector instructions, etc.
There were some copying and I think they settled with AMD licensing the Intel FSB for $$$ (they switched to DEC Alpha bus protocol when the AMD Athlon 64 bit era came around).
With the AMD 64 they licensed it back to Intel when it became clear that Itanuim was dead as it was so slow and Microsoft forced Intel's hand by releasing a version for Windows Server.
The market is big enough for both.
Yep, but they're both willing to use the patents to keep other entrants out.
I believe that the person you're replying to is referring to an attempt to produce x86 compatible processors that Nvidia undertook when they bought the license that Via owned.
IIRC that didn't go so well for Nvidia because the license didn't include new parts of the instruction set like the 64 bit instructions that AMD made in the mid 2000s and AMD wouldn't license them.
So there's a reason why they'd prefer x86. Hopefully they manage to release an ARM competitor for the desktop market, though with AI boom, it seems more likely that it will be a server focused on supporting their GPU lineup.
Graviton's certainly work out better for every program I have tried on AWS (obviously this is mainly because AWS set the price to ensure they do).
I mean the are complex x86 programs that run just as fast for longer on battery on a M1 then a comparable Dell/Lenovo.
So competing on server grade gpu might be more difficult for intel.
I would love to see Intel get somewhere but they are dead last among the major players.
CUDA isn't that important any more.
The weird one was that Aurora at 2 exaflops using.. Intel Max?
But the bottom is where volume and profits are. If the PC market has shown us anything, it’s that only producing for the top of the market gets you outcompeted.
Getting paid a small yearly salary for every one of your products may look really nice but the size of the market makes it a precarious business.
The only other place where I saw a considerable number of Mac deployments was university. So portraying it as a niche product for media people has some truth in it but is in my opinion far from the whole truth.
Intel competing in the midrange is far from a nothingburger.
I really wish someone would give Nvidia some effective competition, but I just don’t see that being Intel.
And what do you expect the driver to say instead?
Also, for graphics cards, I expect every feature requires some work from the driver. It’s not as if OpenGL is a hardware interface.
A critical feature for game engines to actually decide what features to use, otherwise instead of 60 FPS, you might get single digit FPS.
https://www.saschawillems.de/creations/opengl-hardware-capab... claims:
“The “OpenGL hardware capability viewer” (short “glCapsViewer) a multi-platform client-side application that reads out all important hardware capabilities of the current OpenGL-implementation present on your system”
Reading its source (https://github.com/SaschaWillems/glCapsViewer/blob/85ee6ab68...), I get the impression it does that by calling either of:
- glGetIntegerv
- glGetInteger64v
- glGetIntegeri_v
- glGetProgramivARB
- glGetFloatv
- glGetString
I think https://registry.khronos.org/OpenGL-Refpages/gl4/html/glGet.... documents all those functions.I don’t see any occurrence of ‘hardware’ on that page. Looking at the data collected by that tool (example: http://opengl.gpuinfo.org/displayreport.php?id=10016), and checking some of the capabilities listed, I can find all I looked at on that page (https://registry.khronos.org/OpenGL-Refpages/gl4/html/glGet....), so I don’t think that tool uses other methods to obtain information (I didn’t read its full source code, though)
Also:
1) https://registry.khronos.org/OpenGL/specs/gl/glspec46.core.p... doesn’t mention ‘capabilities’, doesn’t mention ‘hardware’ much, and even says
“While an implementation of OpenGL may be hardware dependent, the Specification is independent of any specific hardware on which it is implemented. We are concerned with the state of graphics hardware only when it corresponds precisely to GL state.”
2) https://community.khronos.org/t/determining-hardware-opengl-... asks “I am trying to find a way for my program to determine (during run time) whether the graphics card supports OpenGL hardware acceleration, and how much RAM is installed on the graphics card”
and
https://community.khronos.org/t/determining-hardware-opengl-... replies: “Sorry, there’s no way in OpenGL to do what you want. You’ll just have to trust the driver to do the right thing.”
Of course, that last reply may be incorrect, but from what I found, I think it is correct.
So, what’s going on? Is the spec unclear about the glGet functions? Am I overlooking a call that _does_ return hardware info? As I said: educate me.
(And of course, “implemented in hardware” does not guarantee anything about performance.)
What did they try? And when?
Arc already has an extremely good value proposition: hardware AV1 encoding - so you can keep your existing GPU (let's face it: it's probably still more than fine) and augment it with a cheap Arc.
Slow developments are fine with me; it's a beautiful card.
I guess CUDA compatible would be fine, but for myself, I'd buy their cards for compute workloads as long as they have some reasonable API regardless of whether it's CUDA or not. If they have something usable based on OpenCL, SYCL, whatever, they would have a shot at getting my money. Ideally that would also include then providing some support to make sure there are usable backends for PyTorch, Tensorflow, etc.
Ah well. Let's see if they can figure this out. Between Intel and AMD, you'd think somebody could step forward and give NVIDIA some serious competition.
They also have arguably pretty good OpenCL support, as well as downstream support for PyTorch and Tensorflow using their custom extensions https://github.com/intel/intel-extension-for-tensorflow and https://github.com/intel/intel-extension-for-pytorch which are actively developed and just recently brought up-to-date with upstream releases.
If Intel is patient to compete for lower grade GPUs for a few years without killing its GPU line, then we might see them competing for the top in the future. And the top is where the big money is. They'll also need a CUDA compatible API to stand a chance, but they have time.
The only thing that saved Intel until now is that Nvidia can't legally produce x86 CPUs, although they tried.
The more competition, the better.