Hi,
nice!
Anyway, the password protocol is pretty simple I would say. No password or
empty are the same (so 0 bytes). You take the password and encrypt (without
the NUL terminator) using given padding, algorithm and key.
Technically you don't need a length due to the padding.
Regards,
Fredian
Hi,
About 11.5 - it is a section in the documentation (spice protocol).
I am trying to implement the server part on my project (LinuxTerminalService ),
https://github.com/AndreyBarmaley/linux-terminal-service-manager
I already have a working vnc and rdp protocols implemented, and I'm
going to add
Hi,
there's no protocol 11.5.
There's no data length markeR, password is zero terminated and encrypted,
if you refer to the default password schema (no SASL).
Can you explain what you are trying to do?
Regards,
Frediano
Il giorno ven 10 set 2021 alle ore 06:51 Andrey Af
ha scritto:
> Hi,
>
Hi,
For encrypted password, there is definitely no data length market?
For example, I don't need a password, authentication is verified by
another part of the code, how can I skip this?
Hello (very fearfully, because I found no list that could be helpful and
this one seems to be for developers...),
I have been trying for a long while now to get my VM machines to perform
well, but I can't seem to get it right. I seem to be suffering from two
issues:
1. remote-viewer / libvir
> Gents , could you please advise - in case of precompiling meson activation
> warning - Build targets in project: 0 is a normal situation?
Unusual but correct, the project consists of headers to be installed,
so nothing to build.
Frediano
___
Spice-
Gents , could you please advise - in case of precompiling meson activation
warning - Build targets in project: 0 is a normal situation?
--
Андрей Фокин___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailm
On Wed, Oct 23, 2019 at 05:52:09AM -0400, Frediano Ziglio wrote:
> >
> > From: Victor Toso
> >
> > ---
> > .gitlab-ci.yml | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> > index da4f512..c7028dd 100644
> > --- a/.gitlab-ci.yml
>
> From: Victor Toso
>
> ---
> .gitlab-ci.yml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index da4f512..c7028dd 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -4,9 +4,10 @@ variables:
>DEPS_COMMON: git libtool ma
From: Victor Toso
Hi, two patches to be squashed if you agree. Both for fedora-autotools
stage in gitlab-ci.
Victor Toso (2):
fixup: gitlab-ci: to be added
fixup: gitlab-ci: to fix after mingw
.gitlab-ci.yml | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
--
2.21.0
From: Victor Toso
---
.gitlab-ci.yml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index da4f512..c7028dd 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -4,9 +4,10 @@ variables:
DEPS_COMMON: git libtool make python3 python3-six redh
From: Victor Toso
So we can check rpm is working fine.
---
.gitlab-ci.yml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index b3fad64..da4f512 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -3,7 +3,7 @@ image: fedora:latest
variables
On 4/12/19 10:47 AM, Victor Toso wrote:
> From: Victor Toso
>
> Before renaming README to README.md and NEWS to CHANGELOG.md, we were
> shipping those files in the tarball.
>
> I'm fixing this in autotools because it is a 'regression' while
> meson.build never had those included.
>
> Acked-by:
From: Victor Toso
Before renaming README to README.md and NEWS to CHANGELOG.md, we were
shipping those files in the tarball.
I'm fixing this in autotools because it is a 'regression' while
meson.build never had those included.
Acked-by: Victor Toso
---
Makefile.am | 5 -
1 file changed, 4
Hi,
On Fri, Apr 12, 2019 at 09:51:08AM -0300, Eduardo Lima (Etrunko) wrote:
> On 4/10/19 7:20 AM, Victor Toso wrote:
> > From: Victor Toso
> >
> > Signed-off-by: Victor Toso
> > ---
> > CHANGELOG.md | 12
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/CHANGELOG.md b/CH
On 4/10/19 7:20 AM, Victor Toso wrote:
> From: Victor Toso
>
> Signed-off-by: Victor Toso
> ---
> CHANGELOG.md | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index c78a58b..67888fd 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -1,3
On 4/10/19 7:20 AM, Victor Toso wrote:
> From: Victor Toso
>
> Signed-off-by: Victor Toso
> ---
> README| 0
> README.md | 27 +++
> 2 files changed, 27 insertions(+)
> delete mode 100644 README
> create mode 100644 README.md
>
> diff --git a/README b/README
> de
On 4/10/19 7:20 AM, Victor Toso wrote:
> From: Victor Toso
>
> Added 193c54c in 2010-02-04 by Alexander Larsson
> Signed-off-by: Victor Toso
> ---
> ChangeLog | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> delete mode 100644 ChangeLog
>
> diff --git a/ChangeLog b/ChangeLog
> delete
On 4/10/19 7:20 AM, Victor Toso wrote:
> From: Victor Toso
>
> Uppercase + prefix to make Gitlab happy and format it properly.
> This should also be the case for all other spice components in Gitlab.
>
> Signed-off-by: Victor Toso
> ---
> NEWS => CHANGELOG.md | 0
> 1 file changed, 0 insertion
On 4/10/19 7:20 AM, Victor Toso wrote:
> From: Victor Toso
>
> Following patches will rename NEWS to CHANGELOG.md due Gitlab
> integration and remove the currently empty ChangeLog.
>
> Signed-off-by: Victor Toso
> ---
> configure.ac | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
On 4/10/19 7:20 AM, Victor Toso wrote:
> From: Victor Toso
>
> Changes from v1:
> - Added gitlab-ci integration, you can see pipeline for this v2
> here: https://gitlab.freedesktop.org/victortoso/spice-protocol/-/jobs/227059
> - Relaxed automake in regards to NEWS, ChangeLog names;
>
> v1: htt
From: Victor Toso
Added 193c54c in 2010-02-04 by Alexander Larsson
Signed-off-by: Victor Toso
---
ChangeLog | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 ChangeLog
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index e69de29..000
--
2.20.1
___
From: Victor Toso
Uppercase + prefix to make Gitlab happy and format it properly.
This should also be the case for all other spice components in Gitlab.
Signed-off-by: Victor Toso
---
NEWS => CHANGELOG.md | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename NEWS => CHANGELOG.md (100%)
From: Victor Toso
Changes from v1:
- Added gitlab-ci integration, you can see pipeline for this v2
here: https://gitlab.freedesktop.org/victortoso/spice-protocol/-/jobs/227059
- Relaxed automake in regards to NEWS, ChangeLog names;
v1: https://lists.freedesktop.org/archives/spice-devel/2019-Ap
From: Victor Toso
Signed-off-by: Victor Toso
---
CHANGELOG.md | 12
1 file changed, 12 insertions(+)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c78a58b..67888fd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,15 @@
+Major changes in 0.14.0
+===
+* B
From: Victor Toso
Signed-off-by: Victor Toso
---
.gitlab-ci.yml | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 .gitlab-ci.yml
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
new file mode 100644
index 000..b3fad64
--- /dev/null
+++ b/.gitlab-ci.yml
@@ -0,0 +
From: Victor Toso
Following patches will rename NEWS to CHANGELOG.md due Gitlab
integration and remove the currently empty ChangeLog.
Signed-off-by: Victor Toso
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 22c6008..b56f4
From: Victor Toso
Signed-off-by: Victor Toso
---
README| 0
README.md | 27 +++
2 files changed, 27 insertions(+)
delete mode 100644 README
create mode 100644 README.md
diff --git a/README b/README
deleted file mode 100644
index e69de29..000
diff --git a/READ
On Wed, Apr 10, 2019 at 09:44:54AM +, Victor Toso wrote:
> From: Victor Toso
>
> Hi,
>
> As per our milestone (let's try to use it often now!), we should be
> doing a release Tomorrow in order to also do a release of
> linux/vd-agent.
>
> Taking this opportunity to make this a little bit mo
From: Victor Toso
Signed-off-by: Victor Toso
---
README| 0
README.md | 27 +++
2 files changed, 27 insertions(+)
delete mode 100644 README
create mode 100644 README.md
diff --git a/README b/README
deleted file mode 100644
index e69de29..000
diff --git a/READ
From: Victor Toso
Uppercase + prefix to make Gitlab happy and format it properly.
This should also be the case for all other spice components in Gitlab.
Signed-off-by: Victor Toso
---
NEWS => CHANGELOG.md | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename NEWS => CHANGELOG.md (100%)
From: Victor Toso
Hi,
As per our milestone (let's try to use it often now!), we should be
doing a release Tomorrow in order to also do a release of
linux/vd-agent.
Taking this opportunity to make this a little bit more friendly to
Gitlab by renaming NEWS to CHANGELOG and adding .md prefix to it
From: Victor Toso
Added 193c54c in 2010-02-04 by Alexander Larsson
Signed-off-by: Victor Toso
---
ChangeLog | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 ChangeLog
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index e69de29..000
--
2.20.1
___
From: Victor Toso
Signed-off-by: Victor Toso
---
CHANGELOG.md | 12
1 file changed, 12 insertions(+)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c78a58b..67888fd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,15 @@
+Major changes in 0.14.0
+===
+* B
Hi
spice-protocol 0.12.15 can be found in
https://www.spice-space.org/download/releases/spice-protocol/spice-protocol-0.12.15.tar.bz2
Major changes in 0.12.15
* Add support for h265 video codec
* qxl_dev: Align QXLRam to 4 bytes
* meson: fix spice-protocol as subproject
Hey,
On Sun, Jan 06, 2019 at 02:12:55PM +0100, ucontacti ss wrote:
> Dear developers,
>
> While I was looking in the packets using Wireshark I saw that the Major and
> Minor version is 2 and not 1 anymore. And there are some discrepancies in
> the Spice protocol v1.0 and the actual value of field
Dear developers,
While I was looking in the packets using Wireshark I saw that the Major and
Minor version is 2 and not 1 anymore. And there are some discrepancies in
the Spice protocol v1.0 and the actual value of fields. Has the protocol
been updated in any way? If yes, where can I find the chan
>
> This was done for configure.ac earlier, but is missing in meson.build
>
> Signed-off-by: Christophe Fergeau
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 5ed4177..31531e2 100644
> --- a/meson.build
> +++ b/mes
This was done for configure.ac earlier, but is missing in meson.build
Signed-off-by: Christophe Fergeau
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 5ed4177..31531e2 100644
--- a/meson.build
+++ b/meson.build
@@ -2,7 +2,7 @@
Hi,
Release was done earlier today.
Package can be found in spice-space webpage [0] or in gitlab [1].
It was signed with my key, 97D9123DE37A484F.
[0] https://www.spice-space.org/download/releases/spice-protocol/
[1] https://gitlab.freedesktop.org/spice/spice-protocol/tags/v0.12.14
toso
Hi,
On Thu, May 31, 2018 at 04:49:59AM -0400, Frediano Ziglio wrote:
> >
> > From: Victor Toso
> >
> > Signed-off-by: Victor Toso
> > ---
> > NEWS | 11 +++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/NEWS b/NEWS
> > index a899aba..78531a3 100644
> > --- a/NEWS
> > +++
>
> From: Victor Toso
>
> Signed-off-by: Victor Toso
> ---
> NEWS | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index a899aba..78531a3 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -1,3 +1,14 @@
> +Major changes in 0.12.14
> +
> +* add str
From: Victor Toso
Hi,
Only pending patch that I can see is [0]. Koji build seems okay [1]
[0] https://lists.freedesktop.org/archives/spice-devel/2018-May/043716.html
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=27319331
Cheers,
toso
Victor Toso (1):
NEWS: prepare for 0.12
From: Victor Toso
Signed-off-by: Victor Toso
---
NEWS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/NEWS b/NEWS
index a899aba..78531a3 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,14 @@
+Major changes in 0.12.14
+
+* add stream-device protocol
+* add SPICE_
Hi,
On Thu, Apr 19, 2018 at 03:19:40AM -0400, Frediano Ziglio wrote:
> >
> > From: Victor Toso
> >
> > This definition is lacking in client while in server it is hardcoded
> > to 50. Having a well defined limitation allow us to make the code
> > more robust and optimized.
> >
> > Signed-off-by
>
> From: Victor Toso
>
> This definition is lacking in client while in server it is hardcoded
> to 50. Having a well defined limitation allow us to make the code
> more robust and optimized.
>
> Signed-off-by: Victor Toso
> ---
> spice/protocol.h | 2 ++
> 1 file changed, 2 insertions(+)
>
From: Victor Toso
This definition is lacking in client while in server it is hardcoded
to 50. Having a well defined limitation allow us to make the code
more robust and optimized.
Signed-off-by: Victor Toso
---
spice/protocol.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/spice/protoc
- Original Message -
> From: ge...@hostfission.com
> To: "Frediano Ziglio"
> Cc: "Christophe Fergeau" ,
> spice-devel@lists.freedesktop.org
> Sent: Saturday, October 14, 2017 8:34:42 AM
> Subject: Re: [Spice-devel] Spice Protocol Missing Head
On 2017-10-13 20:05, Frediano Ziglio wrote:
> I tried a few years back (spice-protocol 0.12.10) to move these code
> generation scripts to spice-protocol, but this did not work out
> nicely so this was reverted.
I found this too, I opted to use the spice.proto file to write my own
header
with t
>
> > I tried a few years back (spice-protocol 0.12.10) to move these code
> > generation scripts to spice-protocol, but this did not work out
> > nicely so this was reverted.
>
> I found this too, I opted to use the spice.proto file to write my own
> header
> with the basics that were required.
I tried a few years back (spice-protocol 0.12.10) to move these code
generation scripts to spice-protocol, but this did not work out
nicely so this was reverted.
I found this too, I opted to use the spice.proto file to write my own
header
with the basics that were required.
I agree that hav
Hey,
On Wed, Oct 11, 2017 at 02:33:00AM +1100, ge...@hostfission.com wrote:
> I just spent the last hour searching for the header that contains "RedInit"
> according to the Spice protocol specification, frustratingly not finding it.
>
> After digging through the client source I finally discovered
I just spent the last hour searching for the header that contains
"RedInit" according to the Spice protocol specification, frustratingly
not finding it.
After digging through the client source I finally discovered it wasn't
renamed to "SpiceInit", but to "SpiceMsgMainInit". Seems the Spice
pr
On Thu, Jul 13, 2017 at 12:04:06PM +0200, Christophe Fergeau wrote:
> On Wed, Jul 12, 2017 at 03:20:53PM -0400, Leo Famulari wrote:
> > Hello,
> >
> > I noticed the release of spice-protocol 0.12.13 doesn't seem to have an
> > associated signature file, which is different from the last few years o
On Wed, Jul 12, 2017 at 03:20:53PM -0400, Leo Famulari wrote:
> Hello,
>
> I noticed the release of spice-protocol 0.12.13 doesn't seem to have an
> associated signature file, which is different from the last few years of
> releases.
>
> Is this a change in policy for spice-protocol?
I believe I
Hello,
I noticed the release of spice-protocol 0.12.13 doesn't seem to have an
associated signature file, which is different from the last few years of
releases.
Is this a change in policy for spice-protocol?
Leo
signature.asc
Description: PGP signature
On 02/21/2017 04:44 PM, Oscar Segarra wrote:
Hi Urii,
What I meant is that VMs can move dynamically bethween hypervisors (or
hosts) and therefore squid configuration may change according to where
VMs are placed on.
If you change the squid configuration dynamically you'll need to
make sure a c
Hi Uri,
If you change the squid configuration dynamically you'll need to
make sure a client can to the VM. That may include migration.
What would be interesting is habing a kind of health check that checks
"Port telnet". And if a port is ready, add dinamically the rule to the
squid server.
Sorr
Hi Urii,
What I meant is that VMs can move dynamically bethween hypervisors (or
hosts) and therefore squid configuration may change according to where VMs
are placed on.
What I can do is opening the whole rank 5634 - 6166 (accodring to
https://access.redhat.com/documentation/en-US/Red_Hat_Enterpr
On 02/21/2017 02:52 PM, Oscar Segarra wrote:
Hi Uri,
The problem comes when VMs can migrate between Hypervisors. It is,
eventually the scenario can turn as follows:
Hypervisor1 (10.0.0.1) <-- Stopped due to maintenance
Hypervisor2 (10.0.0.2)
VM1 (port 5900)
VM2 (port 5901)
VM3 (port
Hi Uri,
The problem comes when VMs can migrate between Hypervisors. It is,
eventually the scenario can turn as follows:
Hypervisor1 (10.0.0.1) <-- Stopped due to maintenance
Hypervisor2 (10.0.0.2)
VM1 (port 5900)
VM2 (port 5901)
VM3 (port 5902)
VM4 (port 5903)
Thanks a lot!
2017
On 02/21/2017 11:04 AM, Oscar Segarra wrote:
Hi Uri,
Thanks a lot for th example... It looks clarify the security/acl but
what I'd like to know is if is there any known configuration for an
scenario like this:
Hypervisor1 (10.0.0.1)
VM1 (port 5900)
VM2 (port 5901)
Hypervisor2 (10.0.0.2)
Thanks a lot Christophe for your clarifications...I will try and I will let
you know!
> 2.- How squid redirects requests to the correct hypervisor (where VM is
> running)
Is this any different than if these were for example http servers
residing on the internal servers? Can't something like
SPICE
On Tue, Feb 21, 2017 at 11:30:03AM +0100, Oscar Segarra wrote:
> Hi Christophe,
>
> I have already read this document... and I'm not able to translate it to
> the scenario I've posted..
>
> In this case I cannot see:
>
> 1.- Where configure ports
Not familiar at all with squid, but I'd expect t
Hi Christophe,
I have already read this document... and I'm not able to translate it to
the scenario I've posted..
In this case I cannot see:
1.- Where configure ports
2.- How squid redirects requests to the correct hypervisor (where VM is
running)
3.- In my environment where I don't have oVirt.
On Tue, Feb 21, 2017 at 10:04:52AM +0100, Oscar Segarra wrote:
> Hi Uri,
>
> Thanks a lot for th example... It looks clarify the security/acl but what
> I'd like to know is if is there any known configuration for an scenario
> like this:
>
> Hypervisor1 (10.0.0.1)
> VM1 (port 5900)
> VM2
Hi Uri,
Thanks a lot for th example... It looks clarify the security/acl but what
I'd like to know is if is there any known configuration for an scenario
like this:
Hypervisor1 (10.0.0.1)
VM1 (port 5900)
VM2 (port 5901)
Hypervisor2 (10.0.0.2)
VM3 (port 5902)
VM4 (port 5903)
Of co
On 02/19/2017 07:33 PM, Oscar Segarra wrote:
Hi Uri,
I have not been able to find the example you suggest... can you paste
the url of the example?
Hi Oscar,
Disclaimer:
This is just an example. There may be better more secure ways
to do it. You should research and decide on a solution
Hi,
On Sun, Feb 19, 2017 at 11:48:44AM +0200, Uri Lublin wrote:
> On 02/19/2017 08:07 AM, Oscar Segarra wrote:
> > Hi,
> >
> > First of all, I'd like to say that I'm not sure enough I'm writing to
> > the correct mailing list, I have not been able to find a common users
> > mailing list.
> >
> >
Hi Uri,
I have not been able to find the example you suggest... can you paste the
url of the example?
Thanks a lot.
2017-02-19 18:23 GMT+01:00 Uri Lublin :
> On 02/19/2017 12:50 PM, Oscar Segarra wrote:
>
>> Hi Uri,
>>
>> Is there any public documentation for configuring the http/https proxy?
>
On 02/19/2017 12:50 PM, Oscar Segarra wrote:
Hi Uri,
Is there any public documentation for configuring the http/https proxy?
In my scenario, I have 2 hypervisors and I don't know exactly how to
redirect each port to each hypervisor.
And regarding your comments, host_ip and host_port (in first
Hi Uri,
Is there any public documentation for configuring the http/https proxy?
In my scenario, I have 2 hypervisors and I don't know exactly how to
redirect each port to each hypervisor.
And regarding your comments, host_ip and host_port (in first and second
command) belong to the reverse proxy
On 02/19/2017 08:07 AM, Oscar Segarra wrote:
Hi,
First of all, I'd like to say that I'm not sure enough I'm writing to
the correct mailing list, I have not been able to find a common users
mailing list.
I'm planning to deploy a VDI solution based on SPICE. I'd like to grant
access through the I
Hi,
First of all, I'd like to say that I'm not sure enough I'm writing to the
correct mailing list, I have not been able to find a common users mailing
list.
I'm planning to deploy a VDI solution based on SPICE. I'd like to grant
access through the Internet to the VDI desktops but I don't want to
From: Yuri Benditovich
Client mode of mouse pointer defined as display capability to
allow easy indication of mouse mode change
Signed-off-by: Yuri Benditovich
---
spice/protocol.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/spice/protocol.h b/spice/protocol.h
index d742eda..a5f9b97 10
>
> From: Victor Toso
>
> Client might want to choose a preferred video codec for streaming for
> different reasons which having hardware decoder support being the most
> interest one.
>
> This message allows the client to send a list of video codecs in a
> order of preference.
>
> Signed-off-
We don't want to maintain more macros than necessary and in the end
the equivalent G_GNUC_XXX macros should be preferred.
Should any project actually depend on these macros they can keep using
them by defining the usual SPICE_DEPRECATED macro until they migrate
away from them or the macros are rein
From: Victor Toso
Client might want to choose a preferred video codec for streaming for
different reasons which having hardware decoder support being the most
interest one.
This message allows the client to send a list of video codecs in a
order of preference.
Signed-off-by: Victor Toso
---
s
From: Yuri Benditovich
Extended QXLRom structure to keep current mouse mode.
Added interrupt status bit to indicate mouse mode change to guest.
Signed-off-by: Yuri Benditovich
---
spice/qxl_dev.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/spice/qxl_dev.h b/spice/qxl_dev.h
index 9e7
From: Victor Toso
Client might want to choose a preferred video codec for streaming for
different reasons which having hardware decoder support being the most
interest one.
This message allows the client to send a list of video codecs in a
order of preference.
Signed-off-by: Victor Toso
---
s
Ack
On Mon, 2016-10-24 at 15:28 +0200, Victor Toso wrote:
> From: Victor Toso
>
> Signed-off-by: Victor Toso
> ---
> configure.ac | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> index dd2d373..17f48d1 100644
> --- a/configure.ac
> +++ b/c
>
> From: Victor Toso
>
> This header is auto generated from spice_codegen.py tool in
> spice-common repository and thus, it changes what was included
> manually.
>
> Move SpiceDataCompressionType struct to comply with spice_codegen.py.
> This header was generated with:
>
> ./spice_codegen.py
From: Victor Toso
This header is auto generated from spice_codegen.py tool in
spice-common repository and thus, it changes what was included
manually.
Move SpiceDataCompressionType struct to comply with spice_codegen.py.
This header was generated with:
./spice_codegen.py -e spice.proto ../spic
From: Victor Toso
Signed-off-by: Victor Toso
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index dd2d373..17f48d1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2,7 +2,7 @@ AC_PREREQ([2.57])
m4_define([SPICE_MAJOR], 0)
m4_
From: Victor Toso
Client might want to choose a preferred video codec for streaming for
different reasons which having hardware decoder support being the most
interest one.
This message allows the client to send a combination of video codec
type with a ranking value of SpiceVideoCodecRank.
Sign
Hi,
On Wed, Oct 19, 2016 at 03:40:18PM -0500, Jonathon Jongsma wrote:
> On Tue, 2016-10-18 at 14:59 +0200, Victor Toso wrote:
> > From: Victor Toso
> >
> > This header is auto generated from spice_codegen.py tool in
> > spice-common repository and thus, it changes what was included
> > manually.
On Tue, 2016-10-18 at 14:59 +0200, Victor Toso wrote:
> From: Victor Toso
>
> This header is auto generated from spice_codegen.py tool in
> spice-common repository and thus, it changes what was included
> manually.
I'm afraid I don't really understand this description.
>
> Move SpiceDataCompre
From: Victor Toso
This header is auto generated from spice_codegen.py tool in
spice-common repository and thus, it changes what was included
manually.
Move SpiceDataCompressionType struct to comply with spice_codegen.py.
This header was generated with:
./spice_codegen.py -e spice.proto ../spic
>
> -New message type for compressed messages has been added to the protocol
> -SPICE_SPICEVMC_CAP_DATA_COMPRESS_LZ4 capability has been added
> ---
> spice/enums.h| 10 ++
> spice/protocol.h | 4
> 2 files changed, 14 insertions(+)
>
> diff --git a/spice/enums.h b/spice/enums.
Hey,
On 05/10/2016 01:23 PM, Victor Toso wrote:
Hi,
On Thu, May 05, 2016 at 02:43:33PM +0300, Snir Sheriber wrote:
-New message type for compressed messages has been added to the protocol
-SPICE_SPICEVMC_CAP_DATA_COMPRESS_LZ4 capability has been added
Let's keep the commit messages under 72 c
On Tue, May 10, 2016 at 12:23:30PM +0200, Victor Toso wrote:
> Hi,
>
> On Thu, May 05, 2016 at 02:43:33PM +0300, Snir Sheriber wrote:
> > -New message type for compressed messages has been added to the protocol
> > -SPICE_SPICEVMC_CAP_DATA_COMPRESS_LZ4 capability has been added
>
> Let's keep the
Hi,
On Thu, May 05, 2016 at 02:43:33PM +0300, Snir Sheriber wrote:
> -New message type for compressed messages has been added to the protocol
> -SPICE_SPICEVMC_CAP_DATA_COMPRESS_LZ4 capability has been added
Let's keep the commit messages under 72 char.
> ---
> spice/enums.h| 10 ++
-New message type for compressed messages has been added to the protocol
-SPICE_SPICEVMC_CAP_DATA_COMPRESS_LZ4 capability has been added
---
spice/enums.h| 10 ++
spice/protocol.h | 4
2 files changed, 14 insertions(+)
diff --git a/spice/enums.h b/spice/enums.h
index c6e9840..cf
-New message type for compressed messages has been added to the protocol
-SPICE_SPICEVMC_CAP_DATA_COMPRESS_LZ4 capability has been added
---
spice/enums.h| 10 ++
spice/protocol.h | 4
2 files changed, 14 insertions(+)
diff --git a/spice/enums.h b/spice/enums.h
index c6e9840..34
On 01/08/2016 11:41 AM, Frediano Ziglio wrote:
On Thu, Jan 07, 2016 at 09:35:34PM +0200, Uri Lublin wrote:
On 01/06/2016 12:26 PM, Christophe Fergeau wrote:
This should make things more portable.
Hi Christophe,
This only works for building with (not too old) gcc.
It would be safer to check
>
> On Thu, Jan 07, 2016 at 09:35:34PM +0200, Uri Lublin wrote:
> > On 01/06/2016 12:26 PM, Christophe Fergeau wrote:
> > >This should make things more portable.
> >
> > Hi Christophe,
> >
> > This only works for building with (not too old) gcc.
> >
> > It would be safer to check that in config
On Thu, Jan 07, 2016 at 09:35:34PM +0200, Uri Lublin wrote:
> On 01/06/2016 12:26 PM, Christophe Fergeau wrote:
> >This should make things more portable.
>
> Hi Christophe,
>
> This only works for building with (not too old) gcc.
>
> It would be safer to check that in configure and
> add a condi
On 01/06/2016 12:26 PM, Christophe Fergeau wrote:
This should make things more portable.
Hi Christophe,
This only works for building with (not too old) gcc.
It would be safer to check that in configure and
add a conditional here.
Thanks,
Uri.
https://bugs.freedesktop.org/show_bug.cgi?
This should make things more portable.
https://bugs.freedesktop.org/show_bug.cgi?id=86997
---
spice/barrier.h | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/spice/barrier.h b/spice/barrier.h
index 710da09..7d63721 100644
--- a/spice/barrier.h
+++ b/spice/barrier.h
@@ -3
On Mon, Oct 5, 2015 at 12:07 PM, Christophe Fergeau wrote:
> They are not arch-specific, so installing them in $libdir is not needed.
ACK!
> ---
> Makefile.am| 2 +-
> python_modules/Makefile.am | 2 +-
> spice-protocol.pc.in | 4 ++--
> 3 files changed, 4 insertions(+), 4
1 - 100 of 279 matches
Mail list logo
