"Arm’s display processors are quite unique as they allow for offloading UI rendering completely to the display processor from the GPU and in doing this achieve very good power efficiency compared to GPU-only approaches."
Please elaborate on this, I have always thought that Android rendering pipelines used the GPU for everything. I assume the display processor handles 2D layers?
Generally the display processors' task is to fetch the frames from the frame-buffer somewhere in the memory and convert to the right protocol (VGA etc) and push it to the display only. Some might include more supports like cropping, re-scaling and other CV operations. However, in Arm's case it allows you to overlay many rendered frames to form a final frame that the UI has - which they call as frame composition. I think this is what is being referred by the author here.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
Facebook
Twitter
RSS
4 Comments
Back to Article
ET - Tuesday, March 6, 2018 - link
Here's to hoping that the G31 indeed replaces the 400/450.PeachNCream - Tuesday, March 6, 2018 - link
"...able to process 2 pixels and 2 texels per cycle."I just got a Riva TNT's "TwiN Texel Engine" flashback reading that.
serendip - Tuesday, March 6, 2018 - link
"Arm’s display processors are quite unique as they allow for offloading UI rendering completely to the display processor from the GPU and in doing this achieve very good power efficiency compared to GPU-only approaches."Please elaborate on this, I have always thought that Android rendering pipelines used the GPU for everything. I assume the display processor handles 2D layers?
karthik.hegde - Tuesday, March 6, 2018 - link
Generally the display processors' task is to fetch the frames from the frame-buffer somewhere in the memory and convert to the right protocol (VGA etc) and push it to the display only. Some might include more supports like cropping, re-scaling and other CV operations. However, in Arm's case it allows you to overlay many rendered frames to form a final frame that the UI has - which they call as frame composition. I think this is what is being referred by the author here.