On Tue, Aug 17, 2010 at 6:31 AM, Alexander Larsson wrote:
> On Fri, 2010-07-30 at 00:20 -0400, Todd Deshane wrote:
>> Hi All,
>>
>> I was just wondering if support for access to an application window
>> only (as opposed to the VM's entire desktop) is a planned feature or
>> if it is even a possibl
- "Alexander Larsson" wrote:
> On Thu, 2010-07-29 at 12:20 -0400, Alon Levy wrote:
> > Changes
> > var = (void**)&val;
> > Into
> > {
> > typeof val* p = &val;
> > var = (void**)p;
> > }
> >
> > Which fixes these warnings (we compile with -Werror, any warning
> breaks compile):
> >
On Tue, 2010-08-03 at 04:39 -0400, Alon Levy wrote:
> Required for full screen in n900. Our vdagent is currently broken in that if
> you request a resolution
> that isn't supported by the driver you are left with a white screen, so this
> fixes "spicec --full-screen=auto-conf"
> for n900.
>
> Re
On Thu, 2010-07-29 at 12:20 -0400, Alon Levy wrote:
> Changes
> var = (void**)&val;
> Into
> {
> typeof val* p = &val;
> var = (void**)p;
> }
>
> Which fixes these warnings (we compile with -Werror, any warning breaks
> compile):
> warning: dereferencing type-punned pointer will break str
On Thu, 2010-07-29 at 09:03 -0400, Alon Levy wrote:
> Patch adds a "from __future__" import that doesn't affect newer python's but
> allows python 2.5.4 to run the code (tested under scratchbox, n900 build
> environment)
Ack, pushed.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
On Mon, 2010-07-26 at 09:18 +0300, Yonit Halperin wrote:
> ---
> server/red_worker.c | 21 +
> 1 files changed, 17 insertions(+), 4 deletions(-)
The changes look ok, but don't you also need to check in
VideoStream::maintenance() if surface is 0 before calling
_channel.inval
On Tue, 2010-08-17 at 14:26 +0300, Yonit Halperin wrote:
> This patch replaces the DirectDraw dependent surfaces allocation with mspace
> malloc.
> (bugzilla #29254).
>
> Future work on this issue can include:
> 1) Tuning mspace for surfaces.
> 2) Separating the deallocations of DEVRAM resources
On Tue, 2010-08-17 at 14:26 +0300, Yonit Halperin wrote:
> The driver no longer claims to support DirectDraw.
> It uses mspace to allocate surfaces and not HeapVidMemAllocAligned.
> This fixes freedesktop bug #29254.
Ack (although you should git rm dd.c too).
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Looking at the release schedule we've obviously missed the 0.6.0
release. This was partly due to vacations and partly due to some other
focuses for a while. However, i think we're pretty good on track for a
0.6.0 release maybe early next week or so.
There are a few outstanding patches that need t
The driver no longer claims to support DirectDraw.
It uses mspace to allocate surfaces and not HeapVidMemAllocAligned.
This fixes freedesktop bug #29254.
---
display/driver.c | 18 ++-
display/qxldd.h | 19 +--
display/res.c| 158 +++---
This patch replaces the DirectDraw dependent surfaces allocation with mspace
malloc.
(bugzilla #29254).
Future work on this issue can include:
1) Tuning mspace for surfaces.
2) Separating the deallocations of DEVRAM resources from those of surfaces.
Currently, there is only one release_ring.
3)
On Fri, 2010-07-30 at 00:20 -0400, Todd Deshane wrote:
> Hi All,
>
> I was just wondering if support for access to an application window
> only (as opposed to the VM's entire desktop) is a planned feature or
> if it is even a possible/intended use for Spice? For example, could it
> work similar to
On Tue, 2010-08-10 at 03:17 -0700, Steven Tan wrote:
> Hi All,
>
>
> I can't find information on minimum HW requirements to run a Spice
> client. Is there some specific information on requirements for CPU,
> RAM, GPU etc. with regard to a Spice client environment?
I don't think we really know th
On Fri, 2010-08-13 at 08:42 +0200, Attila Sukosd wrote:
> Hi Darren,
>
> Not yet, I havent really had the time. As far as I've seen, other than
> the limited libraries, the graphics and audio will definitely need
> reimplementing, since androids don't run X11 or ALSA. It might be
> possible to por
On Aug 10, 2010, at 6:17 PM, Steven Tan wrote:
Hi All,
I can't find information on minimum HW requirements to run a Spice client. Is
there some specific information on requirements for CPU, RAM, GPU etc. with
regard to a Spice client environment?
Thanks
Steve
__
15 matches
Mail list logo
