Hi All,
QXL-WDDM-DOD 0.13 has been released.
Changes in this version:
1. Driver license switched to Apache v2
2. Versioning scheme improved and version number embedded into driver binaries
The latest QXL-WDDM-DOD source code available at:
https://gitlab.com/spice/qxl-wddm-dod
Source tarball fo
On Fri, Oct 21, 2016 at 01:40:38PM +0100, Frediano Ziglio wrote:
> Add an utility to make possible to check various features of
> VideoEncoder.
> 2 GStreamer plugins are used in a chain like this:
> (1) input pipeline -> (2) video encoder -> (3) output pipeline
> While converting output from (1)
This seems unchanged from the previous version?
What I asked in
https://lists.freedesktop.org/archives/spice-devel/2016-October/032971.html
cannot be changed?
Christophe
On Fri, Oct 21, 2016 at 01:40:39PM +0100, Frediano Ziglio wrote:
> Signed-off-by: Frediano Ziglio
> ---
> server/tests/gst-te
On Fri, Oct 21, 2016 at 01:40:37PM +0100, Frediano Ziglio wrote:
> Signed-off-by: Frediano Ziglio
> ---
> server/gstreamer-encoder.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/server/gstreamer-encoder.c b/server/gstreamer-encoder.c
> index 53dfb98..d8437e4 1006
From the commit log, I have no idea why/how they were tested now. If you
tested them locally, just mention this in the log.
Acked-by: Christophe Fergeau
Christophe
On Fri, Oct 21, 2016 at 01:40:35PM +0100, Frediano Ziglio wrote:
> Signed-off-by: Frediano Ziglio
> ---
> server/gstreamer-encod
Am 07.11.2016 um 09:10 schrieb Christophe Fergeau:
On Fri, Nov 04, 2016 at 08:48:48PM +0100, Thorsten Kohfeldt wrote:
Binary builds can be found at
https://copr.fedorainfracloud.org/coprs/teuf/spice-mingw/build/473299/
Nice offer,
but I'm a little confused by that plethora of choices:
3 targ
Am 07.11.2016 um 10:21 schrieb Christophe Fergeau:
On Mon, Nov 07, 2016 at 10:07:58AM +0100, Thorsten Kohfeldt wrote:
BTW,
_all_ binaries' details state 'Version 0.5.1.0, copyright RH 2009'.
Here it would make sense to auto update with the build number, right ?
Now only one build will be mad
> Try by myself the FlexVDI driver. Yes, the problem is client/server mouse.
> With FlexVDI, even with our agent installed client mouse is working.
> Stopping the agent make even FlexVDI mouse slow (is easy to see the issue
increasing
> the network latency).
> Not tried to change in our driver E
On Tue, 2016-11-08 at 10:49 +0100, Christophe Fergeau wrote:
> On Wed, Nov 02, 2016 at 04:27:19PM -0500, Jonathon Jongsma wrote:
> >
> > On Wed, 2016-11-02 at 16:36 +0100, Francois Gouget wrote:
> > >
> > > Signed-off-by: Francois Gouget
> > > ---
> > > src/udscs.h | 5 +++--
> > > 1 file chang
On Wed, Nov 02, 2016 at 04:27:19PM -0500, Jonathon Jongsma wrote:
> On Wed, 2016-11-02 at 16:36 +0100, Francois Gouget wrote:
> > Signed-off-by: Francois Gouget
> > ---
> > src/udscs.h | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/src/udscs.h b/src/udscs.h
>
> When the QXL driver receives a QXL_INTERRUPT_CLIENT_MONITORS_CONFIG
> interrupt,
> we currently always notify userspace that there was some hotplug event.
>
> However, gnome-shell/mutter is reacting to this event by attempting a
> resolution change, which it does by issueing drmModeRmFB, drmMod
Hey,
Here is what should hopefully be the final version of this series, only change
since v3 is that I made sure to keep "PATCH" in the subject line, and I added
missing Acked-by/Signed-of-by annotations to the logs.
Christophe
___
Spice-devel mailing
When the QXL driver receives a QXL_INTERRUPT_CLIENT_MONITORS_CONFIG interrupt,
we currently always notify userspace that there was some hotplug event.
However, gnome-shell/mutter is reacting to this event by attempting a
resolution change, which it does by issueing drmModeRmFB, drmModeAddFB,
and t
qxl_crtc_set_from_monitors_config() is defined in qxl_drv.h but never
implemented.
Signed-off-by: Christophe Fergeau
Acked-by: Frediano Ziglio
---
drivers/gpu/drm/qxl/qxl_drv.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h b/drivers/gpu/drm/qxl/qxl_drv.h
in
They are not used outside of their respective source file
Signed-off-by: Christophe Fergeau
Acked-by: Frediano Ziglio
---
drivers/gpu/drm/qxl/qxl_cmd.c | 2 +-
drivers/gpu/drm/qxl/qxl_display.c | 4 ++--
drivers/gpu/drm/qxl/qxl_drv.h | 3 ---
3 files changed, 3 insertions(+), 6 deletion
It's always returning 0, and it's always ignored.
Signed-off-by: Christophe Fergeau
Acked-by: Frediano Ziglio
---
drivers/gpu/drm/qxl/qxl_drv.h | 2 +-
drivers/gpu/drm/qxl/qxl_gem.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h b/drivers/g
The message has to be terminated by a newline as it's not going to get
added automatically.
Signed-off-by: Christophe Fergeau
Acked-by: Frediano Ziglio
---
drivers/gpu/drm/qxl/qxl_fb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/qxl/qxl_fb.c b/drivers/gpu
The use of drm_cvt_mode() in qxl_add_monitors_config_modes() means that
the resolutions we are going to present to user-space are going to be
rounded down to a multiple of 8. In the QXL arbitrary resolution case,
this is not useful.
This commit forces the actual width/height that was requested by t
qdev->gem.objects was initialized directly in qxl_device_init() rather
than going through qxl_gem_init(), and qxl_gem_fini() was never called.
Signed-off-by: Christophe Fergeau
---
drivers/gpu/drm/qxl/qxl_kms.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm
19 matches
Mail list logo
