Active Topics

 


Reply
Thread Tools
benny1967's Avatar
Posts: 3,790 | Thanked: 5,718 times | Joined on Mar 2006 @ Vienna, Austria
#431
A different aspect of the topic of this thread:

Are the slides of Marc's presentation available somewhere? I thought they were a really nice overview if Jolla so far.
 

The Following 2 Users Say Thank You to benny1967 For This Useful Post:
Stskeeps's Avatar
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:
Posts: 1,298 | Thanked: 2,277 times | Joined on May 2011
#433
Originally Posted by Stskeeps View Post
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.
So, does it mean that Intel's driver on the desktop isn't good either? So how does it work now? Or X.org dependencies have different performance situation than Intel's driver that can be used for Wayland?

At least if that's going to improve in the future, things can get better with newer kernels / Mesa.

Originally Posted by Stskeeps View Post
It may shock a few to discover that IA-Android doesn't actually use Mesa for Android.
Are those drivers from Intel closed?
 

The Following User Says Thank You to shmerl For This Useful Post:
Posts: 2,076 | Thanked: 3,268 times | Joined on Feb 2011
#434
Originally Posted by Stskeeps View Post
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 real question is:
candy crush in 60 fps?

Just hope this time you manage to get a good deal for the hackers out there, no locked bootloaders and images for recovery and stuff
 

The Following User Says Thank You to szopin For This Useful Post:
Stskeeps's Avatar
Posts: 1,671 | Thanked: 11,478 times | Joined on Jun 2008 @ Warsaw, Poland
#435
Originally Posted by shmerl View Post
So, does it mean that Intel's driver on the desktop isn't good either? So how does it work now? Or X.org dependencies have different performance situation than Intel's driver that can be used for Wayland?

At least if that's going to improve in the future, things can get better with newer kernels / Mesa.



Are those drivers from Intel closed?
https://github.com/android-ia/hardware_intel_ufo

Could be worse.
 

The Following 14 Users Say Thank You to Stskeeps For This Useful Post:
Posts: 1,548 | Thanked: 7,510 times | Joined on Apr 2010 @ Czech Republic
#436
Originally Posted by Stskeeps View Post
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.
Sure that perfectly understandable and I'm totally fine with that! I'll just be happy as long as someone who does have the time and/or the requirements can hack together what is needed to get it working with "normal" open source drivers on their own (or for their distro).
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
 

The Following 2 Users Say Thank You to MartinK For This Useful Post:
vistaus's Avatar
Posts: 423 | Thanked: 478 times | Joined on Sep 2014 @ Netherlands
#437
Originally Posted by Rauha View Post
Decided finally not to get one.

-(Almost) no need
-Wifi only
-How badly Jolla handled the phone pre-orders last year.

But its six months until release and obviously they will have "regular" sales later on. Maybe buy one when they are in shops.

Really wanting a new model Jolla phone though.
But a new Jolla Phone will also go through pre-order so that means you'll be not buying it.
 

The Following User Says Thank You to vistaus For This Useful Post:
Posts: 45 | Thanked: 78 times | Joined on Dec 2013 @ Bruxelles
#438
Hello guys. I think nieldk need help. I just found this https://www.indiegogo.com/projects/j...rtup/x/9179347 .
Let's help him
 

The Following 9 Users Say Thank You to b.cloanta For This Useful Post:
Posts: 1,400 | Thanked: 3,751 times | Joined on Sep 2009 @ Arctic cold of northern .fi
#439
Originally Posted by vistaus View Post
But a new Jolla Phone will also go through pre-order so that means you'll be not buying it.
I doubt that it will be Wifi only being a phone and I actually need one.

Anyway, you fanbois should try to allow at least bit of criticism. Jolla did screw up their last pre-order shipments big time. Its ok to say so. Try not to have a panick attack if some one points to the fact.
 

The Following 2 Users Say Thank You to Rauha For This Useful Post:
Posts: 67 | Thanked: 79 times | Joined on May 2012 @ Germany
#440
Originally Posted by wicket View Post
It also means full OpenGL acceleration (not GL ES) via Mesa.
Are you sure about that? I mean, theoretically it's possible - but will it be so implemented in Sailfish?

Best regards,

Jaracz
__________________
And the story continues...

Nokia 5110 --> Nokia 3210 --> Nokia 8210 --> Nokia 7250i --> Nokia 6500 Slide --> Nokia N97 mini --> Nokia N9 --> BB Z30 --> Jolla C
 
Reply

Tags
bulks


 
Forum Jump


All times are GMT. The time now is 02:49.