On Thu, Jan 28, 2010 at 4:49 AM, Jan Fokkelman
wrote:
> Hi,
> I've got spice working locally but how do I connect from a remote windows
> workstation?
> Locally, if I start the guest I can do:
> spicec -h 127.0.0.1 -p 5930 and it works.
> On a remote windows workstation I do
> spicec -h ip_of_gues
2010/1/11 Frédéric Grelot :
> Did you mean F13 or F12?
> The files in the folder you mentionned are specified "*-0.0.6-0.1.fc13.*.rpm".
>
> Or do you mean that they are F12-compatible?
oh good point, they should work fine in F12 or F13.
Dave.
>
> Frederic.
>
&
>>
>> http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl
>>
>> is where we will be developing a QXL driver for X.org, at the moment there
>> is just an import of the RHEL5 driver which doesn't work out of the box on
>> F12,
>>
>> I've pushed an f12-hackup branch which is a quick hack but I onl
On Mon, Jan 11, 2010 at 6:24 AM, Dave Airlie wrote:
> On Sun, Jan 10, 2010 at 8:33 PM, Christian Lensch wrote:
>> Hi,
>>
>>
>>
>> first of all I would like to say that I am very impressed with the work you
>> doing here. Spice really rocks!
>>
>
On Sun, Jan 10, 2010 at 8:33 PM, Christian Lensch wrote:
> Hi,
>
>
>
> first of all I would like to say that I am very impressed with the work you
> doing here. Spice really rocks!
>
> I have successfully managed to set up an XPPRO-guest on Fedora 12 without
> major problems. With the qxl-drivers
Hi,
Where is the requirement for the 64-bit atomicity in the server code?
I'm not seeing any obvious pointers via grep for atomic, the serial numbers?
it would be nice to document this somewhere (not the requirement but
where the code is).
Dave.
On Thu, Dec 31, 2009 at 1:17 AM, Yaniv Kamay wrote:
> Jonatas Rocha Ribeiro wrote:
>> Good afternoon!
>>
>> I'm having problems compiling the spice for fedora-12 i686, is there a
>> package already compiled for you, or could help me.
>
> 1. We do not provide 32bit packages for F12, we provide yum
>
>> >> I haven't had much time to review the code, but it would be nice if
>> we
>> >> could
>> >> start a qxl interface document that isn't qxl.h, something
>> specifying
>> >> behaviour,
>> >>
>> >> The main thing I'm wondering is how the guest sees these offscreen
>> >> surfaces?
>> >
>> > It i
>> I haven't had much time to review the code, but it would be nice if we
>> could
>> start a qxl interface document that isn't qxl.h, something specifying
>> behaviour,
>>
>> The main thing I'm wondering is how the guest sees these offscreen
>> surfaces?
>
> It is the guest drive responsiebility t
On Tue, Dec 22, 2009 at 1:22 PM, Izik Eidus wrote:
> Hey, please review this patch.
>
I haven't had much time to review the code, but it would be nice if we could
start a qxl interface document that isn't qxl.h, something specifying behaviour,
The main thing I'm wondering is how the guest sees t
On Thu, Dec 24, 2009 at 1:33 AM, Izik Eidus wrote:
> On Wed, 23 Dec 2009 10:04:03 +1000
> Dave Airlie wrote:
>
>> Just wondering why the spice BIOS sets up an MTRR at this point,
>>
>> When X starts and tries to setup a write combining mtrr on the video
>> device
Just wondering why the spice BIOS sets up an MTRR at this point,
When X starts and tries to setup a write combining mtrr on the video
device it throws an
error because it conflicts with this.
Dave.
--
This SF.Net email i
On Wed, Dec 23, 2009 at 6:57 AM, Izik Eidus wrote:
> On Wed, 23 Dec 2009 06:29:30 +1000
> Dave Airlie wrote:
>
>> On Tue, Dec 22, 2009 at 10:00 PM, Yaniv Kamay
>> wrote:
>> > Hi,
>> >
>> > All QXL structures are defined as packed see qxl_dev.
On Tue, Dec 22, 2009 at 10:00 PM, Yaniv Kamay wrote:
> Hi,
>
> All QXL structures are defined as packed see qxl_dev.h.
>
This will prove interesting in the future I expect, unaligned accesses
are really
really slow on certain hw platforms, this is fine when you are
designing for x86 only,
but for
Do we have any plans or forsee upstream wanting to use the QXL interface
on any non-x86 hw (like ppc).
If so qxl.h has a lot of structs which have non-portable structure
packing on non-x86 64-bit targets.
uint32_t x
uint64_t y
ends up aligned different on different archs, on some you
get
uint32
15 matches
Mail list logo
