On Mon, 25 Oct 2010 17:13:58 +0300, Pauli Nieminen
ext-pauli.niemi...@nokia.com wrote:
There isn't API that allows application atomically query for msc changes
and schedule swaps. If msc changes dramatically between query and
scheduling application would schedule swap to happen at wrong time.
On 28/10/10 21:12 +0200, ext Alex Deucher wrote:
On Thu, Oct 28, 2010 at 2:20 PM, Mario Kleiner
mario.klei...@tuebingen.mpg.de wrote:
On Oct 28, 2010, at 6:02 PM, Jesse Barnes wrote:
On Thu, 28 Oct 2010 18:47:09 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
Most of what
On 27/10/10 17:57 +0200, ext Jesse Barnes wrote:
On Wed, 27 Oct 2010 17:15:28 +0200
Mario Kleiner mario.klei...@tuebingen.mpg.de wrote:
On Oct 26, 2010, at 7:08 PM, Jesse Barnes wrote:
On Tue, 26 Oct 2010 19:19:11 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
On Thu, 28 Oct 2010 18:47:09 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
Most of what you have in (b) is pretty straightfoward; even the shared
drawable case shouldn't be too bad, since each X connection could have
bits indicating whether the counter has been picked up after a
On 28/10/10 18:06 +0200, Ville Syrjälä wrote:
On Thu, Oct 28, 2010 at 05:47:09PM +0200, ext Pauli Nieminen wrote:
One option would be adding crct id parameter to calls.
glXGetMscBaseRateOML would return rate, base msc and pipe id where this msc
value is valid. Now all MSC calls would
On Thu, Oct 28, 2010 at 05:47:09PM +0200, ext Pauli Nieminen wrote:
One option would be adding crct id parameter to calls.
glXGetMscBaseRateOML would return rate, base msc and pipe id where this msc
value is valid. Now all MSC calls would take the returned pipe id as
parameter. If pipe id
On Oct 28, 2010, at 6:02 PM, Jesse Barnes wrote:
On Thu, 28 Oct 2010 18:47:09 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
Most of what you have in (b) is pretty straightfoward; even the
shared
drawable case shouldn't be too bad, since each X connection could
have
bits
On Thu, Oct 28, 2010 at 2:20 PM, Mario Kleiner
mario.klei...@tuebingen.mpg.de wrote:
On Oct 28, 2010, at 6:02 PM, Jesse Barnes wrote:
On Thu, 28 Oct 2010 18:47:09 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
Most of what you have in (b) is pretty straightfoward; even the shared
On Oct 26, 2010, at 7:08 PM, Jesse Barnes wrote:
On Tue, 26 Oct 2010 19:19:11 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
SGI_video_sync:
The kernel maintains a video sync counter for
each physical hardware pipe in a system; the counter is incremented
upon the completion of the
On 26/10/10 03:00 +0200, ext Mario Kleiner wrote:
On Oct 25, 2010, at 6:52 PM, Jesse Barnes wrote:
On Mon, 25 Oct 2010 17:13:58 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
There isn't API that allows application atomically query for msc
changes
and schedule swaps. If
On Tue, 26 Oct 2010 11:39:11 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
On 26/10/10 03:00 +0200, ext Mario Kleiner wrote:
On Oct 25, 2010, at 6:52 PM, Jesse Barnes wrote:
On Mon, 25 Oct 2010 17:13:58 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
There
On 26/10/10 17:41 +0200, ext Jesse Barnes wrote:
On Tue, 26 Oct 2010 11:39:11 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
On 26/10/10 03:00 +0200, ext Mario Kleiner wrote:
On Oct 25, 2010, at 6:52 PM, Jesse Barnes wrote:
On Mon, 25 Oct 2010 17:13:58 +0300
Pauli
On Tue, 26 Oct 2010 19:19:11 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
SGI_video_sync:
The kernel maintains a video sync counter for
each physical hardware pipe in a system; the counter is incremented
upon the completion of the display of each full frame of video data. An
There isn't API that allows application atomically query for msc changes
and schedule swaps. If msc changes dramatically between query and
scheduling application would schedule swap to happen at wrong time.
Because of API limitations driver has to make msc increment for each
vblank affecting the
On Mon, 25 Oct 2010 17:13:58 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
There isn't API that allows application atomically query for msc changes
and schedule swaps. If msc changes dramatically between query and
scheduling application would schedule swap to happen at wrong time.
On Oct 25, 2010, at 6:52 PM, Jesse Barnes wrote:
On Mon, 25 Oct 2010 17:13:58 +0300
Pauli Nieminen ext-pauli.niemi...@nokia.com wrote:
There isn't API that allows application atomically query for msc
changes
and schedule swaps. If msc changes dramatically between query and
scheduling
On 07/10/10 00:35 +0200, ext Mario Kleiner wrote:
On Oct 6, 2010, at 1:05 PM, Pauli Nieminen wrote:
There isn't API that allows application atomically query for msc
changes
and schedule swaps. If msc changes dramatically between query and
scheduling application would schedule swap to
There isn't API that allows application atomically query for msc changes
and schedule swaps. If msc changes dramatically between query and
scheduling application would schedule swap to happen at wrong time.
Because of API limitations driver has to make msc increment for each
vblank affecting the
On Oct 6, 2010, at 1:05 PM, Pauli Nieminen wrote:
There isn't API that allows application atomically query for msc
changes
and schedule swaps. If msc changes dramatically between query and
scheduling application would schedule swap to happen at wrong time.
Because of API limitations driver
19 matches
Mail list logo
