Displaying 4 results from an estimated 4 matches for "xa_integer".
Did you mean:
na_integer
2010 Aug 05
0
[PATCH] drmmode: Add backlight support
...rror, %d\n",
+ err);
+
+ /* Set the current value of the backlight property */
+ data = drmmode_output->backlight_active_level;
+ err = RRChangeOutputProperty(output->randr_output,
+ drmmode->backlight_atom,
+ XA_INTEGER, 32, PropModeReplace,
+ 1, &data, FALSE, TRUE);
+ if (err != 0)
+ xf86DrvMsg(output->scrn->scrnIndex, X_ERROR,
+ "RRChangeOutputProperty error, %d\n", err);
+
+ err = RRChangeOutputProperty(output->randr_output,
+ drmmod...
2013 Jun 06
1
[PATCH 1/2] nouveau/mode: split out create_ranged_atom
...->randr_output, *atom,
+ FALSE, TRUE, immutable,
+ 2, atom_range);
+ if (err != 0) {
+ xf86DrvMsg(output->scrn->scrnIndex, X_ERROR,
+ "RRConfigureOutputProperty error, %d\n", err);
+ }
+ err = RRChangeOutputProperty(output->randr_output, *atom,
+ XA_INTEGER, 32, PropModeReplace, 1, &value, FALSE, TRUE);
+ if (err != 0) {
+ xf86DrvMsg(output->scrn->scrnIndex, X_ERROR,
+ "RRChangeOutputProperty error, %d\n", err);
+ }
+}
+
+static void
drmmode_output_create_resources(xf86OutputPtr output)
{
drmmode_output_private_ptr dr...
2009 Aug 12
4
TV-out modesetting DDX patches
[PATCH 1/3] kms: Don't hardcode the output properties
[PATCH 2/3] kms: Implement output->get_property when RandR1.3 is available.
[PATCH 3/3] kms: Add TV-out support
src/drmmode_display.c | 403 ++++++++++++++++++++++++++++++++-----------------
1 files changed, 261 insertions(+), 142 deletions(-)
2008 Jul 06
3
[Bug 16624] New: invalid pointer past to RRChangeOutputProperty
....org
CC: keithp at keithp.com
Created an attachment (id=17547)
--> (http://bugs.freedesktop.org/attachment.cgi?id=17547)
proposed patch for the issue
In nv_output:
error = RRChangeOutputProperty(output->randr_output, dithering_atom,
XA_INTEGER, 32, PropModeReplace, 1,
&nv_output->dithering,FALSE, FALSE);
&nv_output->dithering is a Boolean, but the property is set up as int32. On big
endian systems, this results in the property set being 0x1000000 instead of
0x1. This currently fails the range check (it can only be 1 or 0)....