Earlier quoted context omitted.
Or PowerVR texture compression, which according to Anandtech is the canonical method for iOS development: "Because Apple’s SoCs have always used GPUs from the same vendor, certain vendor-specific features like PowerVR Texture Compress (PVRTC) are widely used in iOS app development" [0] http://www.anandtech.com/show/11243/apple-developing-custom-...
They could easily force change on the app for such change. Look at what they're doing regarding Bitcode and how quickly it might become the default.
Discussions with Apple regarding license agreement
141–150 of 201 posts
Re: Discussions with Apple regarding license agreement
#142Earlier quoted context omitted.
Why has open source been so successful on the CPU then? Branch prediction, say, is no less a patent minefield than GPU framebuffer tiling. Yet gcc and LLVM have no trouble shopping optimizers. This is an excuse, basically. They just don't want to because they fear revenue lost to compatible implementations.
Those are compilers. What open source CPU is there?
The only secrets left are the bits responsible for turning OpenGL (or Vulkan now, I guess) calls into programs to run on the GPU.
Re: Discussions with Apple regarding license agreement
#143Earlier quoted context omitted.
AMD did, however, sell Adreno to Qualcomm when money was tight after the ATI purchase.
And looking back it wasn't a smart decision. Adreno=Radeon
https://www.xda-developers.com/a-look-back-at-amds-history-a...
Re: Discussions with Apple regarding license agreement
#144In the GPU space it is impossible to not infringe on the IP of other vendors. In fact it is the major reason GPU vendors give for not having an open source driver. I have spoken to the CTO (Jem Davies) of ARM about the GPU drivers and open sourcing them more than once. And every time I've gotten the reply: "No, we can't, it opens us up to IP infringement suits." Full disclosure: I used to work in the ARM GPU division…
I have heard that ARM has not been too pleased with IMG buying MIPS and competing directly with ARM. Perhaps ARM would license their GPU patents to Apple and provide some IP protection. Apple could also license patents from AMD. They don't compete directly.
Re: Discussions with Apple regarding license agreement
#145If Apple takes advantage of the depressed stock price to turn around and buy them, it would not be the first time. https://en.m.wikipedia.org/wiki/P.A._Semi
Re: Discussions with Apple regarding license agreement
#146Re: Discussions with Apple regarding license agreement
#147Earlier quoted context omitted.
Both Nvidia and AMD have already switched or are moving towards tile based rendered to reduce bandwidth (and hence energy) costs.
Source? That's a huge architectural change for them.
Re: Discussions with Apple regarding license agreement
#148This is interesting: "Imagination believes that it would be extremely challenging to design a brand new GPU architecture from basics without infringing its intellectual property rights, accordingly Imagination does not accept Apple’s assertions." Could Apple not be using someone else's IP, for example from NVidia or AMD?
AMD does not license to third parties, neither does Intel. Options (ignoring acquisition and design from scratch) are: * NVidia's Tegra graphics cores, possibly (not clear whether they block-license let alone architecture-license to third parties) * ARM's Mali, definitely licensable * Broadcom's VideoCore, possibly * Vivante, definitely licensable * Qualcomm's Adreno, formerly Imageon, unlikely Also note that at leas…
https://www.extremetech.com/computing/227059-amd-announces-n...
Re: Discussions with Apple regarding license agreement
#149Keep in mind this is not just hardware but software related. Right now I have IT graphics tools to optimize 3D models for mobile devices (for example). For us developers, it means optimizing to a different standard, while worrying about backward 'optimization compatibility'. Plus we'll need new software tools for development on the new GPU.
I imagine the new GPU will support the same Metal API. As this is probably something that Apple has been working on for a while now I'd assume that Metal was designed with this new GPU architecture in mind. How much of those tools would need to be updated to a new GPU assuming the current API was specifically written for it ?
I don't really know if that would be the case though, I don't know anything about GPUs.
Re: Discussions with Apple regarding license agreement
#150I wonder how likely it is for Apple to support Vulkan on its hardware.