Re: [PD-dev] pbo transfert WAS: GEM passing output image later.

2012-02-29 Thread chris clepper
On Wed, Feb 29, 2012 at 4:52 AM, Cyrille Henry wrote: > > > Le 29/02/2012 09:34, IOhannes m zmoelnig a écrit : > > and both [pix_texture] and [pix_snap] allow for asynchronous >> DMA-transfers already (though i only added PBO-tarnsfers to [pix_snap] a >> week ago or so). >> it's not really docum

Re: [PD-dev] pbo transfert WAS: GEM passing output image later.

2012-02-29 Thread Cyrille Henry
oh, i thought the pbo message was to use a specific pbo Id. since it's how many PBO to use, on a specific pix_texture or pix_snap, then my question was irrelevant. ok for the ring buffer: possible latency vs possible performance gain, and computer specific tuning. i'll try that as soon as i can.

Re: [PD-dev] pbo transfert WAS: GEM passing output image later.

2012-02-29 Thread IOhannes m zmoelnig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-02-29 10:52, Cyrille Henry wrote: > > > Le 29/02/2012 09:34, IOhannes m zmoelnig a écrit : > >> and both [pix_texture] and [pix_snap] allow for asynchronous >> DMA-transfers already (though i only added PBO-tarnsfers to [pix_snap] a >> week

[PD-dev] pbo transfert WAS: GEM passing output image later.

2012-02-29 Thread Cyrille Henry
Le 29/02/2012 09:34, IOhannes m zmoelnig a écrit : and both [pix_texture] and [pix_snap] allow for asynchronous DMA-transfers already (though i only added PBO-tarnsfers to [pix_snap] a week ago or so). it's not really documented anywhere (yet), but you can send a [pbo $1( message to both these