Ok , i will use a desktop processor to try again .
But do the errors : "virtio 3d acceleration is not supported" and "egl: no drm
render node available , Failed to initializa EGL render node for SPICE GL"
result from hardware devices only or some error configurations ?
-- Or
On 07/11/2017 01:49, Christophe Fergeau wrote:
One note here, when running a wayland spice-gtk/remote-viewer, the only
scroll events I'm getting are GDK_SCROLL_SMOOTH events, I'm not getting
any scroll event until I add GDK_SMOOTH_SCROLL_MASK to the events
spice-gtk listens to (which results in
On 11/07/2017 06:15 PM, Frediano Ziglio wrote:
Fedora 26 removed dependency from python-pyparsing/python-six
to python but we require the executable to run some scripts
Signed-off-by: Frediano Ziglio
Acked-by: Uri Lublin
---
.gitlab-ci.yml | 5 -
1 file changed, 4 insertions(+), 1 d
>
> Frediano Ziglio writes:
>
> > Reduce the needs to buffer the entire frame and than send
> > and on the other end to wait the entire frame before processing.
> > Some encodings allow to start processing before having a full
> > frame allowing to reduce latency and buffering with huge frames.
>
This flag will allow the client to perform some optimisations
on output and buffering processing.
Old clients will ignore this additional flag.
Signed-off-by: Frediano Ziglio
---
spice.proto | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
Changes since v1:
- explain how to avoid
Fedora 26 removed dependency from python-pyparsing/python-six
to python but we require the executable to run some scripts
Signed-off-by: Frediano Ziglio
---
.gitlab-ci.yml | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
Changes since v1:
- use python 3 packages
See https://gitlab.com
On Tue, Nov 07, 2017 at 03:17:31PM +, Frediano Ziglio wrote:
> Fedora 26 removed dependency from python-pyparsing/python-six
> to python but we require the executable to run some scripts
I'd much prefer that this explicitly installs python3-pyparsing/python3-six
(python3 being the future ;). T
Fedora 26 removed dependency from python-pyparsing/python-six
to python but we require the executable to run some scripts
Signed-off-by: Frediano Ziglio
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 6074a3d2..40c4dac5
Frediano Ziglio writes:
>>
>> Frediano Ziglio writes:
>>
>> > Is just used by ring_remove, no reason to have it.
>>
>> Nack. I think there is a good reason: the code and its intent is much
>> clearer with a "ring_remove" name.
>>
>
> Don't get it... are you saying __ring_remove name is more clear
Frediano Ziglio writes:
> There's no need for the canvas operations to be changed.
> This allows without casts to have the operation structures
> constants in the code.
> This potentially allows to reduce attack surface having some
> more data constant instead or read/write.
>
> Signed-off-by: Fr
The idea of Virgl is to use the host card GPU 3D capabilities to
accelerate/provide 3D rendering.
Your card is mainly a 2D VGA card, really useful for remote system
administration but quite useless for Virgl.
Desktop processors integrate an Intel GPU which is enough for Virgl.
About ATI/NVIDI
There's no need for the canvas operations to be changed.
This allows without casts to have the operation structures
constants in the code.
This potentially allows to reduce attack surface having some
more data constant instead or read/write.
Signed-off-by: Frediano Ziglio
---
common/canvas_base.
>
> Frediano Ziglio writes:
>
> > Is just used by ring_remove, no reason to have it.
>
> Nack. I think there is a good reason: the code and its intent is much
> clearer with a "ring_remove" name.
>
Don't get it... are you saying __ring_remove name is more clear than
ring_remove ?
>
> >
> > S
On Tue, Nov 7, 2017, 12:20 PM Christophe de Dinechin <
christophe.de.dinec...@gmail.com> wrote:
> Frediano Ziglio writes:
>
> > From: Jakub Janků
> >
> > This is required for the following GMainLoop integration,
> > which utilizes some of the new functions/definitions, namely:
> >
> > [definition
>
> Frediano Ziglio writes:
>
> > This flag will allow the client to perform some optimisations
> > on output and buffering processing.
> > Old clients will ignore this additional flag.
> >
> > Signed-off-by: Frediano Ziglio
> > ---
> > spice.proto | 3 ++-
> > 1 file changed, 2 insertions(+),
Frediano Ziglio writes:
> Just a style change, the variable does not help readability.
>
> Signed-off-by: Frediano Ziglio
Acked-by: Christophe de Dinechin
> ---
> common/ring.h | 10 ++
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/common/ring.h b/common/ring.h
>
Frediano Ziglio writes:
> There's no need for the canvas operations to be changed.
> This allows without casts to have the operation structures
> constants in the code.
> This potentially allows to reduce attach surface having some
Typo: "attack surface". And you are really talking about the com
Frediano Ziglio writes:
> Is just used by ring_remove, no reason to have it.
Nack. I think there is a good reason: the code and its intent is much
clearer with a "ring_remove" name.
>
> Signed-off-by: Frediano Ziglio
> ---
> common/ring.h | 11 +++
> 1 file changed, 3 insertions(+),
Frediano Ziglio writes:
> From: Jakub Janků
>
> This is required for the following GMainLoop integration,
> which utilizes some of the new functions/definitions, namely:
>
> [definition][GLib version]
> g_clear_pointer() 2.34
> G_SOURCE_REMOVE 2.32
> G_SOURCE_CONTINUE 2.32
> g_unix_signal
Frediano Ziglio writes:
> This flag will allow the client to perform some optimisations
> on output and buffering processing.
> Old clients will ignore this additional flag.
>
> Signed-off-by: Frediano Ziglio
> ---
> spice.proto | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff
Frediano Ziglio writes:
> Reduce the needs to buffer the entire frame and than send
> and on the other end to wait the entire frame before processing.
> Some encodings allow to start processing before having a full
> frame allowing to reduce latency and buffering with huge frames.
>
> Signed-off-
Frediano Ziglio writes:
> Reduce the needs to buffer the entire frame and than send
> and on the other end to wait the entire frame before processing.
I think that you want a little more than "reduce the need", making
explicit what is allowed. Something like: "When both server and
client have th
Is just used by ring_remove, no reason to have it.
Signed-off-by: Frediano Ziglio
---
common/ring.h | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/common/ring.h b/common/ring.h
index 4b0e313..036c098 100644
--- a/common/ring.h
+++ b/common/ring.h
@@ -70,19 +70,14
Just a style change, the variable does not help readability.
Signed-off-by: Frediano Ziglio
---
common/ring.h | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/common/ring.h b/common/ring.h
index 036c098..1ed3576 100644
--- a/common/ring.h
+++ b/common/ring.h
@@ -82,
There's no need for the canvas operations to be changed.
This allows without casts to have the operation structures
constants in the code.
This potentially allows to reduce attach surface having some
more data constant instead or read/write.
Signed-off-by: Frediano Ziglio
---
common/canvas_base.
25 matches
Mail list logo
