These patches address failures in Windows Hardware Lab Tests:
Requirement for EDID data
Requirement for refresh rate of 75/60 Hz
Now the driver contains data in EDID format and reports it to the system
In order to report refresh rate the driver reports support for
VSync control, reports refresh
When the video mode is changed and then the driver disabled and
enabled, it did not enumerate available video modes with lower
resolution than current one. All modes starting from 1024x768
should be available regardless what is current resolution
on driver startup
Signed-off-by: Yuri Benditovich
Concentrate filling of signal info in single procedure.
Fill signal info with specific or default frequency data
according to the global flag of VSync support.
Note that the state of this flobal flag must be defined only
on driver startup and it can't be changed later.
Signed-off-by: Yuri Benditov
Solves failure of HLK "Test for EDID requirements"
EDID contains capabilities and manufacturer data of
the emulated display device. Main parameters are:
Manufacturer code: QXL
Product ID: 0001
Working frequency: 75 Hz
Signed-off-by: Yuri Benditovich
---
qxldod/QxlDod.cpp | 50 +++
In case the driver supports VSync control feature the driver
maintains timer for VSync interrupt indication.
In further commits this timer can be started upon class
driver request.
Signed-off-by: Yuri Benditovich
---
qxldod/QxlDod.cpp | 64 +++
QXL rev.4 device sends interrupts to guest system and they
should be synchronized with VSync interrupt indication to avoid
failure to queue DPC when real interrupt happens.
When the driver needs to raise VSync interrupt indication to OS
it checks active interrupts in hardware and in any case stops
With default period of VSync interrupt notification
(1sec/refresh rate) the driver with device rev.4
has a problem when the system starts running after
restart. Until the issue is solved we set the notification
period to 200 ms, with this value both rev.3 and rev.4
function correctly. Final decisio
Declare VSync control related procedure and set global
flag indicating VSync support for Win10 RS1 and Win8.1
For earlier builds of Win10 (TH1 and TH2) we do not
enable VSync to avoid problem when display is turned off
due to idle setting.
Signed-off-by: Yuri Benditovich
---
qxldod/driver.cpp |
On 02/10/2017 01:40 PM, Bernice Levin wrote:
Hi Guys (Dolls)
Please I need your help. I have installed KVM Hypervisor on OpenSUSE, I
have everything working – installed VMs and have accessed them on
localhost through Virt-viewer but cannot get access on the network from
a windows 10 PC on remo