835926 - Tracking bug for Raspberry Pi graphics performance

Status: RESOLVED DUPLICATE of bug 1662253

(Core :: Graphics, defect)

Description

[George Wright (:gw280) (needinfo me!)]

This is a bug to track work that would affect Raspberry Pi performance. This is a 700MHz ARMv6 board with a Broadcom VideoCore IV GPU.

Comment 1

[Nick Cameron [:nrc]]

Not graphics, but see bug 836486 for JS/RaspPi goodness.

Comment 2

[Josh Reynolds]

Since there's so many issues with X, the Raspberry Pi Foundation has officially announced (http://www.raspberrypi.org/archives/tag/wayland) that it will be abandoning it for Wayland support instead. So for full resolution this bug now Depends on: 635134

Comment 3

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Note to the audience of this bug: for the gonk-flavored FFOS on Rpi (as opposed to the previous bringup), bug 1084624 will pretty much turn on all the gecko fast-paths right out of the box.  The mesa/gallium-based ARM-only GL stack is where long-term support is headed.  It's not ready yet, neither for Raspbian nor FFOS, but there are lots of ways to contribute for those so inclined.

Comment 4

[Jukka Jylänki]

Tried this on my rpi2 for giggles via the raspbian-provided "apt-get install iceweasel" package (FF 45), noticed that WebGL acceleration is not available.

Raspberry Pi doesn't support native OpenGL all that well, but its GPU is OpenGL ES 2.0 compliant, with EGL, which is the same API set that Android GPU-accelerated graphics uses. EGL is not a "selfstanding" API, but requires a tiny bit of interaction with the native windowing system. In this case, interacting with X or Wayland is not needed, but Raspberry Pi has its own VideoCore API "Dispmanx" that is used in conjunction with EGL to initialize GLES 2.0 access, http://elinux.org/Raspberry_Pi_VideoCore_APIs.

Comment 5

[Gregory Pappas [:gregp]]

Bug 1662253 has newer, more relevant dependents.