If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Comment

This seems quite useful because Android's compositor mixes overlay and framebuffer rendering to improve performance and reduce power consumption.

which weston does too ;-)

The big concern is that we end up with a bunch of devices out there with no fbdev or drm/kms driver, and instead a custom non-standard thing. This sort of divergence of android will potentially be a big problem for anyone who wants to put something other than android on their device.

Comment

Interesting, I wasn't aware of that. I thought Weston can use OpenGL (ES) *or* overlays to do compositing, but noth both at the same time with runtime switching.

The big concern is that we end up with a bunch of devices out there with no fbdev or drm/kms driver, and instead a custom non-standard thing. This sort of divergence of android will potentially be a big problem for anyone who wants to put something other than android on their device.

Well, the standard thing sort of is HWComposer, isn't it? Although it does not cover all what KMS does, and is very removed from the Linux kernel standard interfaces.

Comment

Interesting, I wasn't aware of that. I thought Weston can use OpenGL (ES) *or* overlays to do compositing, but noth both at the same time with runtime switching.

Yup, weston can combine both. Of course, it really needs atomic pageflip to be perfect. But with atomic pageflip, you need to use a debug mode (which puts a translucent solid color overlay over what is drawn by the gpu) in order to tell the difference between what is gpu and what is hw overlay.

Comment

Yup, weston can combine both. Of course, it really needs atomic pageflip to be perfect. But with atomic pageflip, you need to use a debug mode (which puts a translucent solid color overlay over what is drawn by the gpu) in order to tell the difference between what is gpu and what is hw overlay.

Hey Rob, I read the mailinglist discussion this morning and maybe you can clear up a few things here... The proposer brought up the issue where under Android is needs a composer of some kind to not get tearing. This reminded me of Keith's talk at linux.conf.au from last year where he said we were losing the idea of a Vsync and were now going to partial-updates-of-the-screen as the new "norm" and the problems it would

It was implied in the mailing lists that KMS couldn't handle that (at least not right now) and that this ADF DID handle it. So I ask you, since you've been doing mobile work, architecturally... can KMS handle Android's needs, or has mobile development shown a crack in the foundations of KMS that would, in your opinion, warrant ADF?

1 like

Comment

Hey Rob, I read the mailinglist discussion this morning and maybe you can clear up a few things here... The proposer brought up the issue where under Android is needs a composer of some kind to not get tearing. This reminded me of Keith's talk at linux.conf.au from last year where he said we were losing the idea of a Vsync and were now going to partial-updates-of-the-screen as the new "norm" and the problems it would

It was implied in the mailing lists that KMS couldn't handle that (at least not right now) and that this ADF DID handle it. So I ask you, since you've been doing mobile work, architecturally... can KMS handle Android's needs, or has mobile development shown a crack in the foundations of KMS that would, in your opinion, warrant ADF?

Hi Ericg, what android (and weston) are missing is the ability to atomically update the primary scanout layer on the same vsync as the overlay layers. It isn't really related to what keithp is doing w/ dri3/present. There are a couple other (mostly minor) things, but it all can and will be added to KMS (and there are already proposals about how to do the atomic pageflip/modeset parts of it). So, can KMS *today* handle android's (and weston's) needs.. no. But what is missing can be added.

1 like

Comment

Hi Ericg, what android (and weston) are missing is the ability to atomically update the primary scanout layer on the same vsync as the overlay layers. It isn't really related to what keithp is doing w/ dri3/present. There are a couple other (mostly minor) things, but it all can and will be added to KMS (and there are already proposals about how to do the atomic pageflip/modeset parts of it). So, can KMS *today* handle android's (and weston's) needs.. no. But what is missing can be added.

No I knew it wasn't related to his work with DRI3/Present, it just got brought up during the Q&A Of his talk at the end and this debate just jogged my memory (unless that question really was related to DRI3 and i misunderstood the original question >_>).

There anything else that was brought up in the ADF debate so far that KMS currently doesn't (but COULD) do? Or perhaps more important... anything that was brought up that KMS CANT do?

1 like

Comment

No I knew it wasn't related to his work with DRI3/Present, it just got brought up during the Q&A Of his talk at the end and this debate just jogged my memory (unless that question really was related to DRI3 and i misunderstood the original question >_>).

There anything else that was brought up in the ADF debate so far that KMS currently doesn't (but COULD) do? Or perhaps more important... anything that was brought up that KMS CANT do?

I think the other major thing he mentioned was scenarios where you need to combine multiple crtc's (currently) to drive ultra high resolution displays. One approach that was brought up was whether this couldn't be accomplished by explicitly exposing primary planes, and using two planes + one crtc. I need to find out more about the hw to see if that makes sense (vs one crtc, multiple encoders, for example). I think there are a couple other features that where not explicitly called out, but could be accomplished via custom (or semi-standard) properties. I don't think anything that KMS *can't* do, otherwise I'd be advocating a new display/modesetting framework ;-)

Which is why I ask haha, technology and ideas advance, assumptions get proven untrue. I know KMS was designed pretty damn recently, but mobile has upset quite a few other trends and thought processes in computing already so I just wanted to make sure that KMS was still holding its own (as far as we know, at least).