Skip to content
Snippets Groups Projects
  1. Aug 28, 2020
    • Thierry Reding's avatar
      nouveau: Support fence FDs · 9921e185
      Thierry Reding authored
      
      Add a new nouveau_pushbuf_kick_fence() function that takes and emits a
      sync fence FD. The fence FD can be waited on, or merged with other fence
      FDs, or passed back to the kernel as a prerequisite for a subsequent HW
      operation.
      
      Based heavily on work by Lauri Peltonen <lpeltonen@nvidia.com>
      
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      9921e185
  2. Aug 27, 2020
  3. Aug 21, 2020
  4. Aug 20, 2020
  5. Jul 08, 2020
  6. Jun 18, 2020
  7. Jun 06, 2020
    • Heiko Thiery's avatar
      xf86drm.c: fix build failure · c7d89412
      Heiko Thiery authored
      
      ./xf86drm.c: In function 'drmNodeIsDRM':
      ../xf86drm.c:2825:7: error: "__FreeBSD__" is not defined [-Werror=undef]
       #elif __FreeBSD__
             ^
      ../xf86drm.c: In function 'drmGetMinorNameForFD':
      ../xf86drm.c:2938:7: error: "__FreeBSD__" is not defined [-Werror=undef]
       #elif __FreeBSD__
             ^
      ../xf86drm.c: In function 'drmParsePciBusInfo':
      ../xf86drm.c:3258:7: error: "__FreeBSD__" is not defined [-Werror=undef]
       #elif __FreeBSD__
             ^
      ../xf86drm.c: In function 'drmParsePciDeviceInfo':
      ../xf86drm.c:3427:7: error: "__FreeBSD__" is not defined [-Werror=undef]
       #elif __FreeBSD__
             ^
      ../xf86drm.c: In function 'drmGetDeviceNameFromFd2':
      ../xf86drm.c:4305:7: error: "__FreeBSD__" is not defined [-Werror=undef]
       #elif __FreeBSD__
             ^
      
      Signed-off-by: default avatarHeiko Thiery <heiko.thiery@gmail.com>
      c7d89412
  8. May 28, 2020
  9. May 27, 2020
  10. May 26, 2020
  11. May 19, 2020
  12. May 07, 2020
  13. May 06, 2020
  14. May 05, 2020
  15. May 04, 2020
  16. Apr 30, 2020
  17. Apr 27, 2020
  18. Apr 26, 2020
  19. Apr 24, 2020
    • Scott Anderson's avatar
      libdrm: Handle usb_interface devices for usb parsing · bf63f8ac
      Scott Anderson authored and Emil Velikov's avatar Emil Velikov committed
      
      Currently the code expects that the device found at
      /sys/char/$maj:$min/device for USB devices is a "usb_device". However,
      at least for some devices, such as for the udl driver, they are instead
      a "usb_interface".
      
      A usb_interface is a child of the usb_device we're interested in, so we
      walk up one in the /sys path to get there.
      
      For example, with a USB device I have, trimmed to show the relevant
      information:
      ```
      $ udevadm info /dev/dri/card1
      P: /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-4/1-4:1.0/drm/card1
      E: DEVTYPE=drm_minor
      $ udevadm info /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-4/1-4:1.0
      E: DEVTYPE=usb_interface
      E: DRIVER=udl
      $ udevadm info /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-4
      E: DEVTYPE=usb_device
      E: DRIVER=usb
      E: BUSNUM=001
      E: DEVNUM=009
      ```
      
      Signed-off-by: default avatarScott Anderson <scott@anderso.nz>
      bf63f8ac
    • Mikhail Golubev's avatar
      xf86drm: Check non-absolute path only for virtio based devices · 57df0757
      Mikhail Golubev authored and Emil Velikov's avatar Emil Velikov committed
      
      This fixes bug in drmParseSubsystemType() that cases situation when
      subsequent call to readlink() from get_subsystem_type() will result in
      EACCESS.
      
      Signed-off-by: default avatarMikhail Golubev <mikhail.golubev@opensynergy.com>
      57df0757
Loading