Thread: Jolla at Slush 2014
View Single Post
Stskeeps's Avatar
Stskeeps is offline Stskeeps
2014-11-19 , 19:57
Posts: 1,671 | Thanked: 11,478 times | Joined on Jun 2008 @ Warsaw, Poland
#432
Originally Posted by shmerl View Post
He said this:



Which means, you need hardware acceleration for the compositor, and for that they'll use Android GPU EGL driver with libhyrbris to run Wayland.

And he said:



All the above sounds like he claims that Intel's kernel driver for their GPU isn't accelerated. I don't get it, since it should be accelerated. So it's really confusing. The bad news - their release will use Android junk blobs for the GPU.
No, that's not what I mean.

What is needed is a quality HW composer library and API, which takes GPU layers together and in a fast way overlays them using a HW part. KMS is still in it's infancy regarding that.

When you use HW composer to compose together GPU buffers/layers (which is a production API one in Android drivers), you also need to use gralloc, which then means you also need to use Android libGLES.

It may very well be possible to get Mesa plus Wayland plus KMS going on the thing. But when it comes to a relatively short HW adaptation period, I'd much prefer to work using known-working hardware adaptation setups and focus on making the experience performant and great for users.

We're dealing with a 2K resolution display here. We need to really push performance.

It may shock a few to discover that IA-Android doesn't actually use Mesa for Android.
 

The Following 29 Users Say Thank You to Stskeeps For This Useful Post: