Hey,
I am running spicy under OSX. If I press the 'a' key, nothing happens
(within the guest). Can you please try if this is the same for you?
Thanks Kai
From: Cliff Sharp csh...@vbridges.com
Date: Wed, 27 Apr 2011 17:10:33 -0500
To: Kai Mosebach kai.moseb...@bsse.ethz.ch
Cc: Kai Mosebach
The slim barebone one :) Without all the gtk overhead...
I think if the audio-interface was more portable it would make a pretty
good starting point for porting.
On 4/29/11 11:05 AM, Christophe Fergeau cferg...@redhat.com wrote:
On Fri, Apr 29, 2011 at 10:56:11AM +0200, Kai Mosebach wrote:
I
On Fri, Apr 29, 2011 at 11:10:02AM +0200, Kai Mosebach wrote:
The slim barebone one :) Without all the gtk overhead...
What overhead?
I think if the audio-interface was more portable it would make a pretty
good starting point for porting.
it? Something requiring X11 osx support isn't good
Split from the xspice rfc patches.
Alon Levy (9):
qxl.h: double include protection
qxl_mem.c: fix pointer arithmatic warning (-Wpointer-arith)
qxl_image.c: fix defined but unused warning
qxl.h: move spice include right after system includes
use spice-protocol defines for ring sizes
---
src/qxl.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/src/qxl.h b/src/qxl.h
index 9451d05..d086ac7 100644
--- a/src/qxl.h
+++ b/src/qxl.h
@@ -27,6 +27,7 @@
#include stdint.h
+#include spice/qxl_dev.h
#include compiler.h
#include xf86.h
#if
---
src/qxl.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/qxl.h b/src/qxl.h
index d086ac7..a2daa8b 100644
--- a/src/qxl.h
+++ b/src/qxl.h
@@ -28,6 +28,7 @@
#include stdint.h
#include spice/qxl_dev.h
+
#include compiler.h
#include xf86.h
#if
Add a qxl_screen_t* member to qxl_ring to make generelizing outb to
ioport_write easier in the next patch. This means we do an extra deref
and addition for every outb, but it means the code becomes simpler for
doing outb in qxl_drv.so and a function call for spiceqxl_drv.so
---
src/qxl.h|
replace everywhere it is needed for xspice - places left out are ifdefed
out later based on the same define mentioned in qxl.h, XSPICE.
note: leave spaces between function name and open paren?
---
src/qxl.h |2 ++
src/qxl_driver.c | 10 +-
src/qxl_ring.c|5 +++--
---
src/qxl.h| 10 ++
src/qxl_driver.c |6 ++
2 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/src/qxl.h b/src/qxl.h
index de3bed7..8f16261 100644
--- a/src/qxl.h
+++ b/src/qxl.h
@@ -83,6 +83,14 @@ typedef struct
typedef struct qxl_surface_t
used in qxl_reset. Later ifdefed with XSPICE, which only uses a single
slot covering all memory (really it should just avoid calling the translation
mechanism, but for now this is simple enough).
---
src/qxl_driver.c | 87 ++
1 files changed,
adds --enable-xspice, which builds an spiceqxl_drv.so target,
and defines SUPPORT_XSPICE. Fails build if spice-server not found.
---
configure.ac| 13 +
src/Makefile.am | 23 +++
2 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/configure.ac
---
src/Makefile.am|1 +
src/qxl.h |8
src/spiceqxl_io_port.c | 12
src/spiceqxl_io_port.h |6 ++
4 files changed, 27 insertions(+), 0 deletions(-)
create mode 100644 src/spiceqxl_io_port.c
create mode 100644 src/spiceqxl_io_port.h
This ifdefs out all the parts in qxl_driver.c that are pci device specific
and are not required by xspice. No functional change. The resulting
spiceqxl_drv.so
doesn't run.
---
src/qxl.h|9 -
src/qxl_driver.c | 89 +-
2 files
Memory is taken from malloc instead of from the pci bar.
Adds shadow_rom to qxl_screen_t.
Introduces init_qxl_rom, which is directly taken from the qxl device
in qemu. Plenty of TODO's added in this commit about various constants
and about factoring out the code to not do this copy paste from
---
src/qxl_driver.c |2 +
src/spiceqxl_io_port.c | 49
src/spiceqxl_io_port.h |4 +++
3 files changed, 55 insertions(+), 0 deletions(-)
diff --git a/src/qxl_driver.c b/src/qxl_driver.c
index fe2f532..ef3139b 100644
---
---
README.xspice | 109
TODO.xspice| 27 +
spiceqxl.xorg.conf | 15 +++
xspice | 21 ++
4 files changed, 172 insertions(+), 0 deletions(-)
create mode 100644 README.xspice
create mode
---
src/qxl_ring.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/src/qxl_ring.c b/src/qxl_ring.c
index 0870ef1..02c4c35 100644
--- a/src/qxl_ring.c
+++ b/src/qxl_ring.c
@@ -75,7 +75,11 @@ qxl_ring_push (struct qxl_ring *ring,
while (header-prod - header-cons
There are companies that only use spicec that don't want to make changes
right now.
On Fri, 2011-04-29 at 10:54 +0200, Christophe Fergeau wrote:
On Thu, Apr 28, 2011 at 03:57:50PM -0500, Cliff Sharp wrote:
I have spice-gtk built and running on OSX. It has some issues but it does
connect. I
On Fri, Apr 29, 2011 at 07:49:14AM -0400, Cliff Sharp wrote:
There are companies that only use spicec that don't want to make changes
right now.
Not on OSX, do they? I'm really not understanding why using spice-gtk seems
to be so bad for you :(
Christophe
pgpByFrLpGmPB.pgp
Description: PGP
I never said that spice-gtk is bad for me.
There are companies that need and use spicec.
On Fri, 2011-04-29 at 14:06 +0200, Christophe Fergeau wrote:
On Fri, Apr 29, 2011 at 07:49:14AM -0400, Cliff Sharp wrote:
There are companies that only use spicec that don't want to make changes
right
On Fri, Apr 29, 2011 at 07:22:12AM -0500, Cliff Sharp wrote:
I never said that spice-gtk is bad for me.
There are companies that need and use spicec.
Once again, why do they *need* it as opposed to they need a spice client,
they don't really care if it's C, python, raw X, Qt, ...
Saying these
Good question...
Here are some recommendations --
There are a number of companies that interface to spicec programmatically.
These companies right now do a fork exec or whatever to run spicec from within
their software products.
There are a number of reasons why they do not implement the spice
Hi,
- Original Message -
There are a number of companies that interface to spicec
programmatically.
These companies right now do a fork exec or whatever to run spicec
from within their software products.
There are a number of reasons why they do not implement the spice
protocol
This is great - thank you
On Apr 29, 2011, at 10:01 AM, Marc-André Lureau wrote:
Hi,
- Original Message -
There are a number of companies that interface to spicec
programmatically.
These companies right now do a fork exec or whatever to run spicec
from within their software
On Tue, Jan 25, 2011 at 07:17:27PM +0100, Marc-André Lureau wrote:
Code adapter from RedPeer::ssl_verify_callback() and used by
spice-gtk.
I looked at this one, and was quickly concerned about the amount of
security checks we're trying to do on our own. Basically, we let openssl do
the
On Tue, Jan 25, 2011 at 07:17:27PM +0100, Marc-André Lureau wrote:
diff --git a/common/ssl_verify.c b/common/ssl_verify.c
new file mode 100644
index 000..f7d9482
--- /dev/null
+++ b/common/ssl_verify.c
@@ -0,0 +1,458 @@
+/* -*- Mode: C; c-basic-offset: 4; indent-tabs-mode: nil -*- */
26 matches
Mail list logo
