On 05/07/13 23:25, Yonit Halperin wrote:
rhbz#968050
In contrast to Microsoft Msdn documentation, the iUniq of a SURFOBJ doesn't
always change when the surface changes. However, it seems that the
iUniq of the associated color_trans (XLATEOBJ) changes, while its
flXlate=XO_TRIVIAL. Since we tried
---
server/tests/test_display_base.c | 25 +++--
1 files changed, 19 insertions(+), 6 deletions(-)
diff --git a/server/tests/test_display_base.c b/server/tests/test_display_base.c
index a4fdae9..3312b11 100644
--- a/server/tests/test_display_base.c
+++ b/server/tests/test_di
---
server/tests/test_empty_success.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/server/tests/test_empty_success.c
b/server/tests/test_empty_success.c
index ccabe6b..0176a52 100644
--- a/server/tests/test_empty_success.c
+++ b/server/tests/test_empty_success
Otherwise, the test exits after the first iteration over all tests,
on the second attempt to create an already created surface.
---
server/tests/test_display_width_stride.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/server/tests/test_display_width_stride.c
b/
optind points to the next argument to parse.
---
server/tests/test_display_base.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/server/tests/test_display_base.c b/server/tests/test_display_base.c
index cf3990f..a4fdae9 100644
--- a/server/tests/test_display_base.c
+++ b
Earlier in this function, test->target_surface is set to 1, which
is the only allowed non-primary surface currently.
If surface parameters are given (and specifically data is checked)
they are being used, otherwise a default surface is used.
Earlier in this function, "command" is set to a non-NUL
When surface_id == 0, primary is used.
Otherwise (currently 1), secondary is used.
Also, remove unused test_width and test_height.
Since commit caea7699434c20dceef8fc79d21b8eeb663fbf53,
test->width and test->height are used.
---
server/tests/test_display_base.c |7 ++-
1 files changed, 2
On 07/08/2013 06:42 PM, Yonit Halperin wrote:
Hi,
On 07/08/2013 06:32 AM, Uri Lublin wrote:
RCC_FOREACH may be dangerous
The following patches replace FOREACH loops with a SAFE version.
Using unsafe loops may cause spice-server to abort (assert fails).
Specifically a read/write fail in those l
On Tue, Jul 9, 2013 at 5:37 PM, bigclouds wrote:
> hi,all
> i want to know on client side, how image data is rendered?
> and the relation among pixman,gtk,cairo,opengl
>
I wrote a post(chinese version :)) in my blog how to implement a spice
client with spice-glib, in this post, I simply researc
hi,all
i want to know on client side, how image data is rendered?
and the relation among pixman,gtk,cairo,opengl
thanks
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
10 matches
Mail list logo