Re: Introduction and updates from NVIDIA

On Tue, Jul 19, 2016 at 11:10:50AM -0700, James Jones wrote: > On 06/13/2016 03:14 AM, Martin Peres wrote: > > On 13/06/16 12:32, Martin Peres wrote: > > > This discussion has been going on for years (not this thread, the general > > > discussion). > > > > Pekka made me realize on IRC that I was n

Re: Introduction and updates from NVIDIA

On 06/13/2016 03:14 AM, Martin Peres wrote: On 13/06/16 12:32, Martin Peres wrote: This discussion has been going on for years (not this thread, the general discussion). Pekka made me realize on IRC that I was not specific enough about what I mean here. By discussion here, I am talking about

Re: Introduction and updates from NVIDIA

On 13/06/16 12:32, Martin Peres wrote: This discussion has been going on for years (not this thread, the general discussion). Pekka made me realize on IRC that I was not specific enough about what I mean here. By discussion here, I am talking about sharing buffers across blocks/drivers/manufac

Re: Introduction and updates from NVIDIA

On 21/03/16 18:28, Miguel Angel Vico wrote: Hi all, First of all, I'd like to introduce myself to the Wayland community: My name is Miguel A. Vico, and I've been working as a Software Engineer for NVIDIA for some time now, more specifically, in the Linux drivers team. Although I've never spoken

Re: Introduction and updates from NVIDIA

On Mon, May 16, 2016 at 11:12:35AM -0700, James Jones wrote: > On 05/16/2016 02:36 AM, Daniel Vetter wrote: > >On Sat, May 14, 2016 at 05:46:51PM +0100, Daniel Stone wrote: > >>On 12 May 2016 at 00:08, James Jones wrote: > >>>The EGLStream encapsulation takes into consideration the new use cases >

Re: Introduction and updates from NVIDIA

On 05/16/2016 02:36 AM, Daniel Vetter wrote: On Sat, May 14, 2016 at 05:46:51PM +0100, Daniel Stone wrote: On 12 May 2016 at 00:08, James Jones wrote: The EGLStream encapsulation takes into consideration the new use cases EGLImage, GBM, etc. were intended to address, and restores what I believ

Re: Introduction and updates from NVIDIA

On Sat, May 14, 2016 at 05:46:51PM +0100, Daniel Stone wrote: > On 12 May 2016 at 00:08, James Jones wrote: > > The EGLStream encapsulation takes into consideration the new use cases > > EGLImage, GBM, etc. were intended to address, and restores what I believe to > > be the minimal amount of the t

Re: Introduction and updates from NVIDIA

Hi James, On 12 May 2016 at 00:08, James Jones wrote: > GBM alone can not perform as well as EGLStreams unless it is extended into > something more or less the same as EGLStreams, where it knows exactly what > engines are being used to produce the buffer content (along with their > current config

Re: Introduction and updates from NVIDIA

On Wed, May 11, 2016 at 4:08 PM, James Jones wrote: > On 05/11/2016 02:31 PM, Daniel Stone wrote: >> >> Hi James, >> >> On 11 May 2016 at 21:43, James Jones wrote: >>> >>> On 05/04/2016 08:56 AM, Daniel Stone wrote: Right - but as with the point I was making below, GBM _right now_ is >>

Re: Introduction and updates from NVIDIA

On Thu, May 12, 2016 at 10:56:33AM +0900, Carsten Haitzler wrote: > On Wed, 11 May 2016 17:13:56 -0700 James Jones said: > > > On 05/11/2016 04:55 PM, Mike Blumenkrantz wrote: > > > > > > > > > On Wed, May 11, 2016 at 7:08 PM James Jones > > > wrote: > > > > > > On

Re: Introduction and updates from NVIDIA

> > While only NVIDIA currently supports streams, this is not an NVIDIA-specific > set of problems, nor is it intended to be an NVIDIA-specific solution if > other vendors adopt the open EGL standards it is based on. > Open standards are great, what's better is open conformance tests, and open imp

Re: Introduction and updates from NVIDIA

On Thu, 12 May 2016 12:30:50 +0300 Pekka Paalanen wrote: > On Wed, 11 May 2016 16:08:13 -0700 > James Jones wrote: > > > On 05/11/2016 02:31 PM, Daniel Stone wrote: > > > Hi James, > > > > > > On 11 May 2016 at 21:43, James Jones wrote: > > >> On 05/04/2016 08:56 AM, Daniel Stone wrote:

Re: Introduction and updates from NVIDIA

On Wed, 11 May 2016 16:08:13 -0700 James Jones wrote: > On 05/11/2016 02:31 PM, Daniel Stone wrote: > > Hi James, > > > > On 11 May 2016 at 21:43, James Jones wrote: > >> On 05/04/2016 08:56 AM, Daniel Stone wrote: > >>> Right - but as with the point I was making below, GBM _right now_ is >

Re: Introduction and updates from NVIDIA

On Wed, 11 May 2016 17:13:56 -0700 James Jones said: > On 05/11/2016 04:55 PM, Mike Blumenkrantz wrote: > > > > > > On Wed, May 11, 2016 at 7:08 PM James Jones > > wrote: > > > > On 05/11/2016 02:31 PM, Daniel Stone wrote: > > > Hi James, > > > > > >

Re: Introduction and updates from NVIDIA

On 05/11/2016 04:55 PM, Mike Blumenkrantz wrote: On Wed, May 11, 2016 at 7:08 PM James Jones mailto:jajo...@nvidia.com>> wrote: On 05/11/2016 02:31 PM, Daniel Stone wrote: > Hi James, > > On 11 May 2016 at 21:43, James Jones mailto:jajo...@nvidia.com>> wrote: >> On 05/0

Re: Introduction and updates from NVIDIA

On Wed, May 11, 2016 at 7:08 PM James Jones wrote: > On 05/11/2016 02:31 PM, Daniel Stone wrote: > > Hi James, > > > > On 11 May 2016 at 21:43, James Jones wrote: > >> On 05/04/2016 08:56 AM, Daniel Stone wrote: > >>> Right - but as with the point I was making below, GBM _right now_ is > >>> mor

Re: Introduction and updates from NVIDIA

On 05/11/2016 02:31 PM, Daniel Stone wrote: Hi James, On 11 May 2016 at 21:43, James Jones wrote: On 05/04/2016 08:56 AM, Daniel Stone wrote: Right - but as with the point I was making below, GBM _right now_ is more capable than Streams _right now_. GBM right now would require API additions t

Re: Introduction and updates from NVIDIA

Hi James, On 11 May 2016 at 21:43, James Jones wrote: > On 05/04/2016 08:56 AM, Daniel Stone wrote: >> Right - but as with the point I was making below, GBM _right now_ is >> more capable than Streams _right now_. GBM right now would require API >> additions to match EGLStreams + EGLSwitch + Stre

Re: Introduction and updates from NVIDIA

On 05/04/2016 08:56 AM, Daniel Stone wrote: Hi, Interleaving both replies ... On 3 May 2016 at 19:44, James Jones wrote: On 05/03/2016 09:53 AM, Daniel Stone wrote: On 3 May 2016 at 17:07, James Jones wrote: No, the necessary extensions can not be contained within the binding. There is not

Re: Introduction and updates from NVIDIA

Hi all, I just sent a second round of patches to add support for EGLStream & friend in Weston. Also, we've uploaded two weston branches that include all these patches on top of weston master branch. You can find them here: https://cgit.freedesktop.org/~jjones/weston/ 'nvidia_head' contains t

Re: Introduction and updates from NVIDIA

Hi, Interleaving both replies ... On 3 May 2016 at 19:44, James Jones wrote: > On 05/03/2016 09:53 AM, Daniel Stone wrote: >> On 3 May 2016 at 17:07, James Jones wrote: >>> No, the necessary extensions can not be contained within the binding. >>> There >>> is not enough information within the dr

Re: Introduction and updates from NVIDIA

On Tue, May 3, 2016 at 11:58 AM, James Jones wrote: > On 05/03/2016 09:58 AM, Daniel Stone wrote: >> >> Hi James, >> >> On 3 May 2016 at 17:29, James Jones wrote: >>> >>> Given Wayland is designed such that clients drive buffer allocation >> >> >> I'd just note that this isn't strictly true. I've

Re: Introduction and updates from NVIDIA

On 05/03/2016 09:58 AM, Daniel Stone wrote: Hi James, On 3 May 2016 at 17:29, James Jones wrote: Given Wayland is designed such that clients drive buffer allocation I'd just note that this isn't strictly true. I've personally implemented Wayland support for platforms (media playback on an ex

Re: Introduction and updates from NVIDIA

On 05/03/2016 09:53 AM, Daniel Stone wrote: Hi James, On 3 May 2016 at 17:07, James Jones wrote: On 04/29/2016 03:07 PM, Daniel Stone wrote: With new Wayland protocol, patches to all Wayland compositors to send proper hints to clients using this protocol, improvements to GBM, and updates to b

Re: Introduction and updates from NVIDIA

On Tue, May 03, 2016 at 09:29:58AM -0700, James Jones wrote: > On 05/03/2016 09:06 AM, Daniel Vetter wrote: > >On Fri, Apr 29, 2016 at 02:16:28PM -0700, James Jones wrote: > >>Streams could provide a way to express that the compositor picked the wrong > >>plane, but they don't solve the optimal con

Re: Introduction and updates from NVIDIA

Hi James, On 3 May 2016 at 17:29, James Jones wrote: > Given Wayland is designed such that clients drive buffer allocation I'd just note that this isn't strictly true. I've personally implemented Wayland support for platforms (media playback on an extremely idiosyncratic platform) where server-s

Re: Introduction and updates from NVIDIA

Hi James, On 3 May 2016 at 17:07, James Jones wrote: > On 04/29/2016 03:07 PM, Daniel Stone wrote: >>> With new Wayland protocol, patches to all Wayland compositors to send >>> proper >>> hints to clients using this protocol, improvements to GBM, and updates to >>> both of these when new GPU arch

Re: Introduction and updates from NVIDIA

On 05/03/2016 09:06 AM, Daniel Vetter wrote: On Fri, Apr 29, 2016 at 02:16:28PM -0700, James Jones wrote: Streams could provide a way to express that the compositor picked the wrong plane, but they don't solve the optimal configuration problem. Configuration is a tricky mix of policy and capabil

Re: Introduction and updates from NVIDIA

On 04/29/2016 03:07 PM, Daniel Stone wrote: Hi James, On 29 April 2016 at 22:16, James Jones wrote: I was on leave when this discussion was started. Now that I'm back, I'd like to respond to a few points raised below: Welcome back! Thanks! On 03/29/2016 09:44 AM, Daniel Stone wrote: Ri

Re: Introduction and updates from NVIDIA

On Fri, Apr 29, 2016 at 02:16:28PM -0700, James Jones wrote: > Streams could provide a way to express that the compositor picked the wrong > plane, but they don't solve the optimal configuration problem. Configuration > is a tricky mix of policy and capabilities that something like HWComposer or >

Re: Introduction and updates from NVIDIA

Hi James, On 29 April 2016 at 22:16, James Jones wrote: > I was on leave when this discussion was started. Now that I'm back, I'd > like to respond to a few points raised below: Welcome back! > On 03/29/2016 09:44 AM, Daniel Stone wrote: >> Right, atomic allows you separate pipe/CRTC configura

Re: Introduction and updates from NVIDIA

I was on leave when this discussion was started. Now that I'm back, I'd like to respond to a few points raised below: On 03/29/2016 09:44 AM, Daniel Stone wrote: Hi Andy, On 23 March 2016 at 00:12, Andy Ritger wrote: Thanks for the thorough responses, Daniel. No problem; as I said, I'm ac

Re: Introduction and updates from NVIDIA

On Wed, 6 Apr 2016 13:14:26 +0100 Daniel Stone wrote: > Hi, > > On 6 April 2016 at 09:41, Jonas Ådahl wrote: > > On Mon, Apr 04, 2016 at 04:27:56PM +0100, Daniel Stone wrote: > >> Again this comes down to the synchronisation. In this case, > >> assuming a mailbox stream: > >> - wl_egl_sur

Re: Introduction and updates from NVIDIA

Hi, On 6 April 2016 at 09:41, Jonas Ådahl wrote: > On Mon, Apr 04, 2016 at 04:27:56PM +0100, Daniel Stone wrote: >> Again this comes down to the synchronisation. In this case, assuming a >> mailbox stream: >> - wl_egl_surface_resize(w1, h1) >> - gl*() >> - eglSwapBuffers() <- commit 1 >>

Re: Introduction and updates from NVIDIA

On Mon, Apr 04, 2016 at 04:27:56PM +0100, Daniel Stone wrote: > Hi, > > On 2 April 2016 at 01:28, Andy Ritger wrote: > > On Tue, Mar 29, 2016 at 05:44:41PM +0100, Daniel Stone wrote: > >> On 23 March 2016 at 00:12, Andy Ritger wrote: > >> > Also, mailbox mode versus FIFO mode should essentially

Re: Introduction and updates from NVIDIA

Hi Miguel, On 2 April 2016 at 11:12, Miguel Angel Vico wrote: > On Fri, 1 Apr 2016 17:28:17 -0700 > Andy Ritger wrote: >> > (As an aside, I wonder if it's properly done in FIFO mode as well; >> > the compositor may very validly choose not to dequeue a buffer if a >> > surface is completely occlu

Re: Introduction and updates from NVIDIA

Hi, On 2 April 2016 at 01:28, Andy Ritger wrote: > On Tue, Mar 29, 2016 at 05:44:41PM +0100, Daniel Stone wrote: >> On 23 March 2016 at 00:12, Andy Ritger wrote: >> > Also, mailbox mode versus FIFO mode should essentially equate to Vsync >> > off versus Vsync on, respectively. It shouldn't have

Re: Introduction and updates from NVIDIA

A couple additions to Andy's comments inline. On Fri, 1 Apr 2016 17:28:17 -0700 Andy Ritger wrote: > On Tue, Mar 29, 2016 at 05:44:41PM +0100, Daniel Stone wrote: > > Hi Andy, > > > > On 23 March 2016 at 00:12, Andy Ritger wrote: > > > Thanks for the thorough responses, Daniel. > > > > No

Re: Introduction and updates from NVIDIA

On Tue, Mar 29, 2016 at 05:44:41PM +0100, Daniel Stone wrote: > Hi Andy, > > On 23 March 2016 at 00:12, Andy Ritger wrote: > > Thanks for the thorough responses, Daniel. > > No problem; as I said, I'm actually really happy to see an > implementation out there. > > > On Tue, Mar 22, 2016 at 01:4

Re: Introduction and updates from NVIDIA

On Fri, Mar 25, 2016 at 08:52:31AM +0900, Carsten Haitzler wrote: > On Tue, 22 Mar 2016 17:12:52 -0700 Andy Ritger said: > > > Maybe I'm not looking in the right place, but where does gbm_surface get > > the intended plane configuration? Are there other display-related flags > > beside GBM_BO_US

Re: Introduction and updates from NVIDIA

On Thu, Mar 24, 2016 at 11:43:51AM -0700, Jasper St. Pierre wrote: > On Thu, Mar 24, 2016 at 10:06 AM, Andy Ritger wrote: > > ... snip ... > > > eglstreams or gbm or any other implementation aside, is it always _only_ > > the KMS driver that knows what the optimal configuration would be? > > It

Re: Introduction and updates from NVIDIA

Hi Andy, On 23 March 2016 at 00:12, Andy Ritger wrote: > Thanks for the thorough responses, Daniel. No problem; as I said, I'm actually really happy to see an implementation out there. > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: >> On 21 March 2016 at 16:28, Miguel Angel Vic

Re: Introduction and updates from NVIDIA

Hi, On 28 March 2016 at 19:12, Daniel Vetter wrote: > On Thu, Mar 24, 2016 at 10:06:04AM -0700, Andy Ritger wrote: >> eglstreams or gbm or any other implementation aside, is it always _only_ >> the KMS driver that knows what the optimal configuration would be? >> It seems like part of the decisio

Re: Introduction and updates from NVIDIA

On Thu, Mar 24, 2016 at 10:06:04AM -0700, Andy Ritger wrote: > On Wed, Mar 23, 2016 at 11:48:01AM +0100, Daniel Vetter wrote: > > On Tue, Mar 22, 2016 at 05:33:57PM -0700, Andy Ritger wrote: > > > On Tue, Mar 22, 2016 at 09:52:21PM +, Daniel Stone wrote: > > > > Hi, > > > > > > > > On 22 March

Re: Introduction and updates from NVIDIA

On Tue, 22 Mar 2016 17:12:52 -0700 Andy Ritger said: > Maybe I'm not looking in the right place, but where does gbm_surface get > the intended plane configuration? Are there other display-related flags > beside GBM_BO_USE_SCANOUT? Then again, the particular plane doesn't > impact us for current

Re: Introduction and updates from NVIDIA

On Thu, Mar 24, 2016 at 10:06 AM, Andy Ritger wrote: ... snip ... > eglstreams or gbm or any other implementation aside, is it always _only_ > the KMS driver that knows what the optimal configuration would be? > It seems like part of the decision could require knowledge of the graphics > hardwar

Re: Introduction and updates from NVIDIA

On Wed, Mar 23, 2016 at 11:48:01AM +0100, Daniel Vetter wrote: > On Tue, Mar 22, 2016 at 05:33:57PM -0700, Andy Ritger wrote: > > On Tue, Mar 22, 2016 at 09:52:21PM +, Daniel Stone wrote: > > > Hi, > > > > > > On 22 March 2016 at 21:43, Daniel Vetter wrote: > > > > On Tue, Mar 22, 2016 at 01:

Re: Introduction and updates from NVIDIA

On Tue, Mar 22, 2016 at 05:33:57PM -0700, Andy Ritger wrote: > On Tue, Mar 22, 2016 at 09:52:21PM +, Daniel Stone wrote: > > Hi, > > > > On 22 March 2016 at 21:43, Daniel Vetter wrote: > > > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: > [...] > > >> I think it's been good to

Re: Introduction and updates from NVIDIA

On Tue, Mar 22, 2016 at 05:12:52PM -0700, Andy Ritger wrote: > Thanks for the thorough responses, Daniel. > > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: > > Secondly, looking at the compositor-drm case, the use of the dumb > > buffer to display undefined content as a dummy modes

Re: Introduction and updates from NVIDIA

On Tue, Mar 22, 2016 at 09:52:21PM +, Daniel Stone wrote: > Hi, > > On 22 March 2016 at 21:43, Daniel Vetter wrote: > > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: [...] > >> I think it's been good to have this series to push the discussion > >> further in more concrete term

Re: Introduction and updates from NVIDIA

Thanks for the thorough responses, Daniel. On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: > Hi Miguel, > > On 21 March 2016 at 16:28, Miguel Angel Vico wrote: > > First of all, I'd like to introduce myself to the Wayland community: My > > name is Miguel A. Vico, and I've been work

Re: Introduction and updates from NVIDIA

Hi, On 22 March 2016 at 21:43, Daniel Vetter wrote: > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: >> 'We don't know when to schedule decompression, because there's no >> explicit barrier' - completely untrue. eglSwapBuffers is that barrier. >> For example, in Freescale i.MX6, th

Re: Introduction and updates from NVIDIA

On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: > On 21 March 2016 at 16:28, Miguel Angel Vico wrote: > I'd like to look at the elephant in the room, which is why you're > using this in the first place (aside from general NVIDIA enthusiasm > for encapsulating everything within EGL St

Re: Introduction and updates from NVIDIA

Hi Miguel, On 21 March 2016 at 16:28, Miguel Angel Vico wrote: > First of all, I'd like to introduce myself to the Wayland community: My > name is Miguel A. Vico, and I've been working as a Software Engineer > for NVIDIA for some time now, more specifically, in the Linux drivers > team. Although

Re: Introduction and updates from NVIDIA

Hello Miguel, I cannot comment on if these patches are within scope of wayland but, I think now is the perfect time to consider API extensions. It would be great if someone with an Nvidia card has time to run performance tests when you submit your patches. A proper decision to include the patches

Introduction and updates from NVIDIA

Hi all, First of all, I'd like to introduce myself to the Wayland community: My name is Miguel A. Vico, and I've been working as a Software Engineer for NVIDIA for some time now, more specifically, in the Linux drivers team. Although I've never spoken before, I've been lately following the amazing