1. 22 Feb, 2019 1 commit
  2. 20 Feb, 2019 2 commits
  3. 19 Feb, 2019 1 commit
  4. 14 Feb, 2019 1 commit
  5. 13 Feb, 2019 3 commits
  6. 30 Jan, 2019 5 commits
  7. 26 Jan, 2019 1 commit
    • A. Wilcox's avatar
      DRI2: Add another Coffeelake PCI ID · d3a26bbf
      A. Wilcox authored
      A user of Adélie Linux reported that modesetting wasn't working properly on
      their Intel i7-9700K-integrated UHD 630 GPU.  Xorg.0.log showed:
      
      [   131.902] (EE) modeset(0): [DRI2] No driver mapping found for PCI device 0x8086 / 0x3e98
      [   131.902] (EE) modeset(0): Failed to initialize the DRI2 extension.
      
      Indeed, that PCI ID is missing from i965_pci_ids.  Adding it fixed the issue
      and allowed the system to work with i965_dri under modesetting.
      d3a26bbf
  8. 16 Jan, 2019 4 commits
  9. 11 Jan, 2019 2 commits
  10. 10 Jan, 2019 4 commits
  11. 09 Jan, 2019 1 commit
    • Olivier Fourdan's avatar
      xwayland: handle case without any crtc · e8295c50
      Olivier Fourdan authored
      
      
      Xwayland creates and destroys the CRTC along with the Wayland outputs,
      so there is possibly a case where the number of CRTC drops to 0.
      
      However, `xwl_present_get_crtc()` always return `crtcs[0]` which is
      invalid when `numCrtcs` is 0.
      
      That leads to crash if a client queries the Present capabilities when
      there is no CRTC, the backtrace looks like:
      
        #0  raise() from libc.so
        #1  abort() from libc.so
        #2  OsAbort() at utils.c:1350
        #3  AbortServer() at log.c:879
        #4  FatalError() at log.c:1017
        #5  OsSigHandler() at osinit.c:156
        #6  OsSigHandler() at osinit.c:110
        #7  <signal handler called>
        #8  main_arena() from libc.so
        #9  proc_present_query_capabilities() at present_request.c:236
        #10 Dispatch() at dispatch.c:478
        #11 dix_main() at main.c:276
      
      To avoid returning an invalid pointer (`crtcs[0]`) in that case, simply
      check for `numCrtcs` being 0 and return `NULL` in that case.
      
      Thanks to Michel Dänzer <michel.daenzer@amd.com> for pointing this as a
      possible cause of the crash.
      Signed-off-by: Olivier Fourdan's avatarOlivier Fourdan <ofourdan@redhat.com>
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <michel.daenzer@amd.com>
      Bugzilla: https://bugzilla.redhat.com/1609181
      e8295c50
  12. 07 Jan, 2019 1 commit
  13. 02 Jan, 2019 1 commit
  14. 21 Dec, 2018 1 commit
  15. 20 Dec, 2018 2 commits
  16. 17 Dec, 2018 5 commits
  17. 14 Dec, 2018 2 commits
  18. 12 Dec, 2018 2 commits
  19. 11 Dec, 2018 1 commit
    • Olivier Fourdan's avatar
      dix: cache ResourceClientBits() value · c7311654
      Olivier Fourdan authored and Adam Jackson's avatar Adam Jackson committed
      
      
      The `LimitClient` is set once and for all at startup, whereas the
      function `ResourceClientBits()` which returns the client field offset
      within the XID based on the value of `LimitClient` can be called
      repeatedly.
      
      Small optimization, cache the result of `ilog2()`, that saves running
      the same loop over and over each time `ResourceClientBits()` is called.
      Signed-off-by: Olivier Fourdan's avatarOlivier Fourdan <ofourdan@redhat.com>
      c7311654