FFe: jockey support for pvr-omap4 (Pandaboard)

Bug #978563 reported by Ricardo Salveti
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Fix Released

Bug Description

PowerVR SGX OpenGL ES driver for Pandaboard is now available at Precise, but still lacks support for jockey.

Having the support will improve the user experience because the user will be able to install the proprietary OpenGL ES 2.0 driver by just using jockey's gtk interface.

This will enable a normal user to activate the Unity 3D experience using the OpenGL ES2.0 support by just following the same procedure already available for other boards like Nvidia and ATI.

Related branches

Revision history for this message
Ricardo Salveti (rsalveti) wrote :
Revision history for this message
Ricardo Salveti (rsalveti) wrote :
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Here I attached 2 debdiffs that would included the support for pvr-omap4. The first one uses the Alternatives class provided by nvidia-common, like done by the other drivers (including fglrx). This is the preferred method to reduce duplicated code, but then nvidia-common needs to be seeded for ARM (package is at least enabled for ARM now) and we'll have one extra package available at the image.

The second patch includes the Alternatives class inside the pvr-omap4 handler itself, and allows it to not depend explicitly at nvidia-common. While it duplicates the class, it doesn't need any extra change and might be a good way to get it included at Precise.

Please review and let me know which would be the preferred way for Precise, so I can then generate the proper merge proposal for the jockey/ubuntu bzr branch.

Revision history for this message
Martin Pitt (pitti) wrote :

I don't really mind whether or not you use the Alternatives class. I think Alberto is a better person to discuss this with.

FFE-wise, approved. It is zero risk for non-OMAP4 systems.

Implementation wise, I have no way to test this, but I assume you did already. I just wonder if it is sufficient to check /proc/cpuinfo for this? Do all omap4 systems use the same graphics chipset and thus this driver?

affects: jockey → jockey (Ubuntu)
Changed in jockey (Ubuntu):
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

Subscribing ubuntu-release as this is a FFE.

Revision history for this message
Oliver Grawert (ogra) wrote :

all omap4 devices we currently support use this chipset (not sure TI even produces different ones) so that should be safe.
in the light of nvidia-common, given that there might be tegra drivers in the future that we want to use this package name for. i would prefer to not seed it for arm atm but keep the option open to make use of nvidia-common for actual nvidia arm bits once we use them (or if that alternative system is really that generic and non nvidia drivers use it, the package should be renamed to jockey-db-common or some such).

i will upload the second patch today if nobody screams at me before ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.9.7-0ubuntu6

jockey (0.9.7-0ubuntu6) precise; urgency=low

  * data/handlers/pvr-omap4.py:
    - Adding handler for PowerVR SGX driver for OMAP 4 based boards, like
      Pandaboard and Blaze (LP: #978563)
 -- Ricardo Salveti de Araujo <email address hidden> Wed, 11 Apr 2012 01:43:02 -0300

Changed in jockey (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.