Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
  • Aaron Plattner Aaron Plattner aplattner
  • Adam Jackson Adam Jackson ajax
  • Alan Coopersmith Alan Coopersmith alanc
  • Alexander Richardson Alexander Richardson arichardson
  • Alex Deucher Alex Deucher agd5f
  • Anuj Phogat Anuj Phogat aphogat
  • Bart Massey Bart Massey BartMassey
  • Ben Widawsky Ben Widawsky bwidawsk
  • Bryce Harrington Bryce Harrington bryce
  • Carlos Garnacho Carlos Garnacho carlosg
  • Christophe Fergeau Christophe Fergeau teuf
  • Chris Wilson Chris Wilson ickle
  • Connor Behan Connor Behan cbehan
  • Cyril Brulebois Cyril Brulebois kibi
  • Damien Lespiau Damien Lespiau damien
  • Daniel Drake Daniel Drake dsd
  • Daniel Stone Daniel Stone daniels
  • Dave Airlie Dave Airlie airlied
  • Dylan Baker Dylan Baker dbaker
  • Egbert Eich Egbert Eich eich
20 authors
  1. Feb 06, 2025
  3. Oct 04, 2024
  5. Sep 30, 2024
  7. Feb 21, 2024
    • Enrico Weigelt, metux IT consult .'s avatar
      uxa: use GCPtr instead of GC * · 1e9b3ac1
      Enrico Weigelt, metux IT consult . authored 
      
Xserver includes have explicit pointer types for quite all kind of structs
(at least those used by drivers), which are used all over the Xserver.
Thus it's much cleaner to use those everywhere.

This commit also clears the road to fix a horrible nightmare of hacks just
needed to circumvent naming clashes between Xserver and Xlib (affecting all
DDXes that are painting on another Xserver): we can simply rename Xserver's
own "GC" type to "GCRec" (the usual naming convention here) and so no trouble
with Xlib's "GC" type anymore. Once this has landed, we're free to do that
without breaking this driver.

Signed-off-by: Enrico Weigelt, metux IT consult .'s avatarEnrico Weigelt, metux IT consult <info@metux.net>
      1e9b3ac1
  9. Oct 06, 2023
  11. Jan 24, 2023
  13. Apr 12, 2022
  15. Apr 06, 2022
  17. Feb 19, 2022
  19. Feb 06, 2022
    • Zoltán Böszörményi's avatar
      Fix a build error with Xorg master · 4e1963a8
      Zoltán Böszörményi authored and Matt Turner's avatar Matt Turner committed 
      
Use xf86ReturnOptValBool() in get_bool_option() instead of
options[option_index].value.bool to fix a compiler error with
current Xorg xserver master branch.

Also use xf86GetOptValInteger() in get_int_option() and
xf86GetOptValString() in get_str_option() for consistency.

The change causes a slight performance drop during option parsing
because the passed-in index_value is no longer used as an index
into the options array.

Instead, it's used as a token now for the standard option getter
functions which works since the index_value to the get_*_option()
functions are identical to the value of options[n].token in the
passed-in OptionInfoRec array.

Also rename "int option_index" to "int token" for clarity in all
three functions.

Signed-off-by: default avatarZoltán Böszörményi <zboszor@gmail.com>
      4e1963a8
  21. Jan 23, 2022
  23. Feb 05, 2020
    • Adam Jackson's avatar
      qxl: Include only the dpms headers we need · 52c421c6
      Adam Jackson authored 
      dpms.h is provided by libXext, but nothing in our configure.ac is
verifying that we have libXext's headers. Fortunately we only need the
definitions in dpmsconst.h (which dpms.h included for us), which is in
xorgproto and thus implied by having an xserver DDK to build against.

And we're even trying to include dpmsconst.h when we think we have it,
meaning when HAVE_XEXTPROTO_71 is defined, but while many other drivers
define that macro in their configure.ac, we for no particularly good
reason do not. Oops. But since xextproto is about ten years old by now
we can probably just safely include it unconditionally.
      52c421c6
  25. Apr 06, 2019
    • Jeremy White's avatar
      Correct a long standing led state bug in XSpice. · 922ec516
      Jeremy White authored and Frediano Ziglio's avatar Frediano Ziglio committed 
      
The CtrlProc for our keyboard driver incorrectly mapped
the device private to a SpiceKbd* intead of to a InputInfoPtr.

That resulted in led state being written into the driver name
for our driver structure, instead of into the led state.

That, in turn, led to a cool bug where if you pressed caps lock,
the two second sync timer in the spice server would cause it to
attempt to correct the state by pressing caps lock to get the
states to match.  Since the states will never match, the caps
lock effectively cycles on and off every two seconds.

Signed-off-by: default avatarJeremy White <jwhite@codeweavers.com>
Acked-by: default avatarVictor Toso <victortoso@redhat.com>
      922ec516
  27. Dec 06, 2018
  29. Nov 18, 2018
  31. Nov 16, 2018
    • Victor Toso's avatar
      qxl: Initialize prev field while dup surface list · cf2254c1
      Victor Toso authored and Christophe Fergeau's avatar Christophe Fergeau committed 
      Otherwise we will can hit a segfault qxl_surface_kill()

 │717     void
 │718     qxl_surface_kill (qxl_surface_t *surface)
 │719     {
 │720         struct evacuated_surface_t *ev = surface->evacuated;
 │721
 │722         if (ev)
 │723         {
 │724             /* server side surface is already destroyed (via reset), don't
 │725              * resend a destroy. Just mark surface as not to be recreated */
 │726             ev->pixmap = NULL;│
 │727             if (ev->image)│
 │728                 pixman_image_unref (ev->image);
 │729             if (ev->next)
 │730                 ev->next->prev = ev->prev;
 │731             if (ev->prev)
>│732                ev->prev->next = ev->next;
 │733             free(ev);
 │734             surface->evacuated = NULL;
 │735             return;
 │736         }

Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1641793



Signed-off-by: default avatarVictor Toso <victortoso@redhat.com>
      cf2254c1
  33. Nov 13, 2018
    • Jonathon Jongsma's avatar
      Make output names match modesetting driver · 64cb597c
      Jonathon Jongsma authored and Christophe Fergeau's avatar Christophe Fergeau committed 
      
The xrandr output name used by the QXL driver is based on the drm
connector type, but the names do not match the kernel names (see
/drivers/gpu/drm/drm_connector.c) or the modesetting driver names (see
hw/xfree86/drivers/modesetting/drmmode_display.c). Making these more
consistent will require less driver-specific special-case code if a user
wants to match an xrandr output to a drm connector.

Note that this patch should not actually change any behavior, since the
QXL driver only uses the 'Virtual' connector type, so this is done only
for consistency.

Signed-off-by: default avatarJonathon Jongsma <jjongsma@redhat.com>
Acked-by: default avatarFrediano Ziglio <fziglio@redhat.com>
      64cb597c
    • Jonathon Jongsma's avatar
      Make output name numbering 1-based · 505a8bb0
      Jonathon Jongsma authored and Christophe Fergeau's avatar Christophe Fergeau committed 
      
The QXL driver names its outputs starting at 0 (e.g. Virtual-0,
Virtual-1, etc). This code was presumably copy/pasted from a different
driver, and is not necessary for the QXL driver. Other drivers simply
use the kernel connector_type_id which starts at 1. For example, the
modesetting driver changed from 0-based names to 1-based names for the
same reason in xserver commit 139e36dd.

This will help to make it easier to identify which xrandr outputs belong
to which drm connector without requiring as many driver-specific
special-cases.

This change might effect custom xorg configurations that references a
specific output name. But the same change was made in modesetting driver
despite that possibility.

Signed-off-by: default avatarJonathon Jongsma <jjongsma@redhat.com>
Acked-by: default avatarFrediano Ziglio <fziglio@redhat.com>
      505a8bb0
  35. Jun 19, 2017
  37. Jun 13, 2017
  39. Apr 07, 2017
  41. Apr 06, 2017
  43. Feb 08, 2017
  45. Dec 19, 2016
  47. Dec 12, 2016