Traditionally, our PowerVR Graphics SDK has been made available through our PowerVR Insider website. For the v3.4 release of our SDK, we wanted to make it as easy as possible to access, modify and integrate it into graphics applications. In addition to the existing downloadable SDK installer, we have started using GitHub as an alternative distribution channel, bringing our SDK to the heart of the developer community. During the process, we’ve also reviewed the SDK license and added an SDK license FAQ to further clarify our terms of use, especially in regards to contributions.

Why distribute through GitHub?

  • GitHub is the go-to website for all things open-source
  • It allows users to easily browse the source, diff commits, and more within a web browser – no downloading required!
  • Users can reap and build the source on embedded development platforms that do not support our installer, e.g. MIPS Creator CI20, ODROID-XU or Pandaboard running Linux
  • Users can easily share code contributions with us for fixes and new features

Which projects are we hosting on GitHub?

Native SDK

This is our cross-platform OpenGL ES 1.x/2.0/3.x SDK, primarily written in C++. It deploys to iOS, Android and Linux devices integrating PowerVR GPUs; it also supports Windows, OS X and Linux PC emulation.

PowerVR Graphics SDK - installer

WebGL SDK

Our WebGL SDK is written in JavaScript. It includes the majority of the features of the native SDK, such as resource loading for the POD, PVR and PFX file formats. It also includes a subset of examples ported from the native SDK, such as the Water demo.

PVRMonitor

This tool is an on-device hardware profiling tool for Android that displays real-time CPU and GPU performance data. It’s the first time we are releasing the source code for this utility!

PowerVR Graphics SDK - PVRMonitor

Community feedback

We believe that GitHub will make it much easier for the community to submit fixes and features to us. Developers can fork the source, apply a change and send a pull request to us. We can then easily review the code change and consider integration.

GitHub also gives us visibility of projects that are extending the SDK, which help us understand how successful the PowerVR Graphics SDK is and if it meets the requirements of our users.

How will we maintain and update the code?

The source will still be developed using our internal source control system. We will update the source on GitHub when each major SDK release goes public every 6 months. We may do interim minor updates (e.g. if we have secondary releases of a major SDK) or apply small fixes for any critical issues that may occur.

When a developer submits a pull request to us, the modified files will be attached to a bug report. A member of our SDK team will then review the change and consider integration with our SDK. A user submitted change applied to our internal source will be pushed to GitHub when our next SDK update goes live.

Make sure you also follow us on Twitter (@ImaginationPR, @PowerVRinsider) for the latest news and announcements from our PowerVR developer ecosystem.

 

Comments

  • Blake Gripling

    Yeah, but perhaps it would be waaaaaay better if you guys would work with developers who are coming up with an open-source PVR driver for Linux and Android systems.

    • mdriftmeyer

      Because that provides a Return on Investment [ROI] for ImgTec when 90% of their valuation comes from Apple?

      They have more motivation with MIPS development by leveraging LLVM/Clang than coordinating with GPL hell to give Android a driver that the OEM will provide.

      Sorry, but I wouldn’t coordinate that with FOSS when I’ve already got OEMs doing the collaborative work, in-house.

      • Blake Gripling

        Figures, as they’re pretty much their biggest client, and as we all know, Apple tends to keep their tech a closely-guarded secret.

        • jo blo

          It would suck for ImgTec if Apple decided to switch away from PVR like they did with the PowerPC back in ’05

        • gianni

          well at one point all macs used ppc and n0w its allx86. Would be really bad business to put all your eggs in one basket. Anyways for open source friendly soc gpus you already have videocore4 and intel hd