make it easier to know what version of the dummy driver is installed (and if it has the required patches)

[totaam]

Issue migrated from trac ticket # 732

component: packaging | priority: minor | resolution: wontfix

2014-11-08 07:43:47: totaam created the issue

---

At the moment, the only way to tell is to check the package database (and assume it is the version in use..) or parse the server output and look for the tell-tale sign:

[245872.234] (II) DUMMY(0): get_constant_dpi_value() found property "dummy-constant-xdpi" with value=96
[245872.234] (II) DUMMY(0): get_constant_dpi_value() found property "dummy-constant-ydpi" with value=96
[245872.234] (II) DUMMY(0): mm(dpi 96x96)=677x423

Things like xvinfo and glxinfo don't help much either.
I don't think we can get that information through the X11 randr protocol either. The only place where the driverName seems to be exported is in ProcDRI2Connect.

We should add a root window property (a bit like what Xvfb does) and stick the version and patch level in there.
Then we can look it up on the server and know what we're dealing with, and emit a warning if it looks outdated.

Code would probably look like this:

	Atom prop = MakeAtom(pProp->name, strlen(pProp->name), TRUE);
	err = dixChangeWindowProperty(serverClient, pWin,
				prop, pProp->type, pProp->format, PropModeReplace,
                                pProp->size, pProp->data, FALSE);

[totaam]

2014-11-08 07:44:27: totaam changed status from new to assigned

[totaam]

2014-11-08 07:44:27: totaam changed owner from antoine to totaam

[totaam]

2014-11-08 07:44:27: totaam edited the issue description

[totaam]

2015-07-03 16:24:16: antoine commented

---

Improvement in r9770: we warn if the DPI is way off.

[totaam]

2016-07-12 17:51:51: antoine commented

---

Milestone renamed

[totaam]

2016-08-21 10:55:50: antoine commented

---

Milestone renamed

[totaam]

2017-02-15 10:01:31: antoine changed status from assigned to closed

[totaam]

2017-02-15 10:01:31: antoine set resolution to wontfix

[totaam]

2017-02-15 10:01:31: antoine commented

---

Best to work on #56 and get that solved.