Linux DRI Development

• Date Index

• [PATCH 1/2] Enhances EDID quirks to allow for specifying and preferring a mode not reported in the EDID block., (continued)
  • [PATCH 1/2] Enhances EDID quirks to allow for specifying and preferring a mode not reported in the EDID block., Dylan Semler
    • Re: [PATCH 1/2] Enhances EDID quirks to allow for specifying and preferring a mode not reported in the EDID block., Alex Deucher
  • Re: Enhance EDID quirks to allow forcing a mode, Dylan Semler
    • Re: Enhance EDID quirks to allow forcing a mode, Daniel Vetter
      • Re: Enhance EDID quirks to allow forcing a mode, Dylan Semler
        • [PATCH v2 0/2] Enhance EDID quirks to allow forcing a mode, Dylan Semler
          • [PATCH v2 1/2] Enhances EDID quirks to allow for specifying and preferring a mode not reported in the EDID block., Dylan Semler
          • [PATCH v2 2/2] Adds EDID force mode quirk for MMT Monitor2Go HD+., Dylan Semler
          • Re: [PATCH v2 0/2] Enhance EDID quirks to allow forcing a mode, Daniel Vetter
    • Re: Enhance EDID quirks to allow forcing a mode, Alex Deucher
      • Re: Enhance EDID quirks to allow forcing a mode, Dylan Semler
        • Re: Enhance EDID quirks to allow forcing a mode, Daniel Vetter
          • Re: Enhance EDID quirks to allow forcing a mode, Dylan Semler
  • [PATCH 2/2] Adds EDID force mode quirk for MMT Monitor2Go HD+., Dylan Semler
• [PATCH REPOST 2] drm: tegra: don't depend on OF, Stephen Warren
  • Re: [PATCH REPOST 2] drm: tegra: don't depend on OF, Rob Clark
    • Re: [PATCH REPOST 2] drm: tegra: don't depend on OF, Stephen Warren
• [PATCH 1/1] drm/exynos: drm_connector: Fix error check condition, Sachin Kamat
  • Re: [PATCH 1/1] drm/exynos: drm_connector: Fix error check condition, Inki Dae
    • Re: [PATCH 1/1] drm/exynos: drm_connector: Fix error check condition, Sachin Kamat
• drm/nouveau: Possible hardware corruption of older GeForce card, Calvin Owens
  • Re: drm/nouveau: Possible hardware corruption of older GeForce card, Ben Skeggs
    • Re: drm/nouveau: Possible hardware corruption of older GeForce card, Calvin Owens
      • Re: drm/nouveau: Possible hardware corruption of older GeForce card, Calvin Owens
        • Re: drm/nouveau: Possible hardware corruption of older GeForce card, Calvin Owens
          • Re: drm/nouveau: Possible hardware corruption of older GeForce card, rh
          • Re: drm/nouveau: Possible hardware corruption of older GeForce card, Ben Skeggs
            • Re: drm/nouveau: Possible hardware corruption of older GeForce card, Calvin Owens
• [PATCH v2] drm/exynos: enable FIMD clocks, Vikas Sajjan
  • Re: [PATCH v2] drm/exynos: enable FIMD clocks, Inki Dae
    • Re: [PATCH v2] drm/exynos: enable FIMD clocks, Vikas Sajjan
• [Bug 10642] via DRM Unimplemented DMA HEADER command (HALCYON_CMDB), bugzilla-daemon
• [Bug 62578] New: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
  • [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!, bugzilla-daemon
• [Bug 62577] New: [r600g] GPU lockup when playing WoW with HD6450 without htile enabled, bugzilla-daemon
  • [Bug 62577] [r600g] GPU lockup when playing WoW with HD6450 without htile enabled, bugzilla-daemon
  • [Bug 62577] [r600g] GPU lockup when playing WoW with HD6450 without htile enabled, bugzilla-daemon
  • [Bug 62577] [r600g] GPU lockup when playing WoW with HD6450 without htile enabled, bugzilla-daemon
• [Bug 62573] New: Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
  • [Bug 62573] [bisected] Half-Life 2: Deathmatch native version crashes, bugzilla-daemon
• Xen guest paravirtualized framebuffer with GEM, Ben Guthro
• freeze with drm/i915, Francesco Allertsen
  • Re: freeze with drm/i915, Daniel Vetter
• [bisected][3.9.0-rc3] NULL ptr dereference from nv50_disp_intr(), Peter Hurley
  • Re: [bisected][3.9.0-rc3] NULL ptr dereference from nv50_disp_intr(), Peter Hurley
    • [PATCH] drm/nouveau: fix NULL ptr dereference from nv50_disp_intr(), Maarten Lankhorst
      • Re: [PATCH] drm/nouveau: fix NULL ptr dereference from nv50_disp_intr(), Aaro Koskinen
      • Re: [PATCH] drm/nouveau: fix NULL ptr dereference from nv50_disp_intr(), Peter Hurley
• [PATCHv2 0/3] PCI Speed Cap Fixes for ppc64, Lucas Kannebley Tavares
  • [PATCHv2 2/3] drm: removed drm_pcie_get_speed_cap_mask function, Lucas Kannebley Tavares
  • [PATCHv2 3/3] ppc64: implemented pcibios_get_speed_cap_mask, Lucas Kannebley Tavares
    • Re: [PATCHv2 3/3] ppc64: implemented pcibios_get_speed_cap_mask, Benjamin Herrenschmidt
  • [PATCHv2 1/3] pci: added pcie_get_speed_cap_mask function, Lucas Kannebley Tavares
    • Re: [PATCHv2 1/3] pci: added pcie_get_speed_cap_mask function, Bjorn Helgaas
      • Re: [PATCHv2 1/3] pci: added pcie_get_speed_cap_mask function, Benjamin Herrenschmidt
        • Re: [PATCHv2 1/3] pci: added pcie_get_speed_cap_mask function, Bjorn Helgaas
  • Re: [PATCHv2 0/3] PCI Speed Cap Fixes for ppc64, Jerome Glisse
• [PATCH] drm/omap: Add device tree support to DMM, Andy Gross
  • Re: [PATCH] drm/omap: Add device tree support to DMM, Rob Clark
• colour pallete utilities, Christopher Harvey
  • Re: colour pallete utilities, Christopher Harvey
• gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses))), Daniel Vetter
  • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses, Alan Stern
    • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses, Daniel Vetter
      • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo, Alan Stern
        • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo, Jiri Kosina
          • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo, Alan Stern
            • [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo)), Jiri Kosina
              • Re: [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo)), Greg KH
              • Re: [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo)), Daniel Vetter
                • Re: [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo)), Jiri Kosina
                  • Re: [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo)), Daniel Vetter
      • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses, Yinghai Lu
        • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses, Jiri Kosina
  • Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses))), Shawn Starr
• [PATCH v4 00/21] modetest enhancements, Laurent Pinchart
  • [PATCH v4 01/21] modetest: Fix warnings, Laurent Pinchart
  • [PATCH v4 02/21] modetest: Remove extern declarations of opt(arg|ind|err|opt), Laurent Pinchart
  • [PATCH v4 03/21] modetest: Sort command line arguments, Laurent Pinchart
  • [PATCH v4 04/21] modetest: Add a command line parameter to select the driver, Laurent Pinchart
    • Re: [PATCH v4 04/21] modetest: Add a command line parameter to select the driver, Ville Syrjälä
      • Re: [PATCH v4 04/21] modetest: Add a command line parameter to select the driver, Laurent Pinchart
  • [PATCH v4 05/21] modetest: Add a command line parameter to drop master after mode set, Laurent Pinchart
  • [PATCH v4 07/21] modetest: Don't limit mode set and planes to two instances, Laurent Pinchart
  • [PATCH v4 06/21] modetest: Retrieve all resources in one go, Laurent Pinchart
  • [PATCH v4 08/21] modetest: Add a command line parameter to set properties, Laurent Pinchart
    • Re: [PATCH v4 08/21] modetest: Add a command line parameter to set properties, Laurent Pinchart
  • [PATCH v4 09/21] modetest: Allow specifying plane position, Laurent Pinchart
    • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Archit Taneja
      • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Laurent Pinchart
        • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Archit Taneja
    • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Ville Syrjälä
      • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Ville Syrjälä
        • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Laurent Pinchart
          • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Ville Syrjälä
        • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Laurent Pinchart
          • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Ville Syrjälä
      • Re: [PATCH v4 09/21] modetest: Allow specifying plane position, Laurent Pinchart
  • [PATCH v4 10/21] modetest: Print the plane ID when setting up a plane, Laurent Pinchart
  • [PATCH v4 11/21] modetest: Remove the -m argument, Laurent Pinchart
  • [PATCH v4 13/21] modetest: Compute CRTC pipe number as needed, Laurent Pinchart
  • [PATCH v4 12/21] modetest: Create a device structure, Laurent Pinchart
  • [PATCH v4 14/21] modetest: Remove the struct connector_arg encoder field, Laurent Pinchart
  • [PATCH v4 15/21] modetest: Store the crtc in the connector_arg structure, Laurent Pinchart
  • [PATCH v4 16/21] modetest: Store the mode in the crtc structure, Laurent Pinchart
  • [PATCH v4 17/21] modetest: Give the CRTC ID to the -P option, Laurent Pinchart
    • Re: [PATCH v4 17/21] modetest: Give the CRTC ID to the -P option, Rob Clark
      • Re: [PATCH v4 17/21] modetest: Give the CRTC ID to the -P option, Laurent Pinchart
  • [PATCH v4 18/21] modetest: Split mode setting and plane setup, Laurent Pinchart
  • [PATCH v4 19/21] modetest: Rename struct connector_arg to struct pipe_arg, Laurent Pinchart
  • [PATCH v4 21/21] modetest: Try all possible encoders for a connector, Laurent Pinchart
  • [PATCH v4 20/21] modetest: Support pipes with multiple connectors, Laurent Pinchart
• [PATCH] drm/exynos: enable FIMD clocks, Vikas Sajjan
  • Re: [PATCH] drm/exynos: enable FIMD clocks, Viresh Kumar
  • Re: [PATCH] drm/exynos: enable FIMD clocks, Sachin Kamat
• Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Maarten Lankhorst
  • Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Dave Airlie
    • Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Maarten Lankhorst
  • Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Chris Wilson
    • Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Maarten Lankhorst
      • Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Maarten Lankhorst
      • Re: [PATCH v2 0/7] xfree86: Handle drm race condition, Chris Wilson
• Re: Stable kernel 3.8.3 appears to break displayport on intel gen4, Bjørn Mork
  • Re: Stable kernel 3.8.3 appears to break displayport on intel gen4, Daniel Vetter
• Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Thomas Meyer
• [PATCH] vesa: Prevent loading if we conflict with a previously loaded driver, Chris Wilson
• [PATCH 0/4] mgag200 fix and cleanup, Christopher Harvey
  • [PATCH 1/4] drm/mgag200: Remove pointless call to drm_fb_get_bpp_depth, Christopher Harvey
  • [PATCH 2/4] drm/mgag200: Pass driver specific mga_device in driver functions, Christopher Harvey
  • [PATCH 3/4] drm/mgag200: Remove extra variable assigns, Christopher Harvey
  • [PATCH 4/4] drm/mgag200: Bug fix: Modified pll algorithm for EH project, Julia Lemire
  • Re: [PATCH 0/4] mgag200 fix and cleanup, Dave Airlie
• [Bug 62466] New: KSP 0.19 causes GPU lockups on r600g, bugzilla-daemon
  • [Bug 62466] KSP 0.19 causes GPU lockups on r600g, bugzilla-daemon
  • [Bug 62466] KSP 0.19 causes GPU lockups on r600g, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
  • [Bug 62466] r600g hyperz lockups with KSP 0.19, bugzilla-daemon
• Revert a bunch of patches in stable kernels, Daniel Vetter
  • Re: Revert a bunch of patches in stable kernels, Daniel Vetter
  • Re: Revert a bunch of patches in stable kernels, Greg KH
• [PATCH] mgag200: fix g200eh pll picking code, Dave Airlie
• [3.9.0-rc2] nouveau deadlock when HDMI TV is connected, Lijo Antony
  • Re: [3.9.0-rc2] nouveau deadlock when HDMI TV is connected, Lijo Antony
• [Bug 62441] New: Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] [r600g] Bastion game runs slowly, bugzilla-daemon
  • [Bug 62441] [r600g] Bastion game runs slowly, bugzilla-daemon
• [Bug 62434] New: [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
  • [Bug 62434] [bisected] 3284.073] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/r600_dri.so failed (/usr/lib/libllvmradeon9.2.0.so: undefined symbol: lp_build_tgsi_intrinsic), bugzilla-daemon
• drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Richard Cochran
  • Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Daniel Vetter
    • Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Richard Cochran
  • <Possible follow-ups>
  • Re: Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Tomas Melin
    • Re: Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Daniel Vetter
      • Re: Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Richard Cochran
        • Re: Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3, Daniel Vetter
          • [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
            • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Richard Cochran
              • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
                • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Richard Cochran
                  • Re: [Intel-gfx] [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
                    • [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
                    • Re: [Intel-gfx] [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Richard Cochran
                      • Re: [Intel-gfx] [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
                        • Re: [Intel-gfx] [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Richard Cochran
                        • Re: [Intel-gfx] [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Richard Cochran
                  • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Tomas Melin
                    • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Tomas Melin
            • [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
              • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Chris Wilson
                • Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring, Daniel Vetter
• Bug report: i915 screens stay blank with 3.8.3, ok with 3.8.2, Stephan Boettcher
  • Re: Bug report: i915 screens stay blank with 3.8.3, ok with 3.8.2, Daniel Vetter
    • Re: Bug report: i915 screens stay blank with 3.8.3, ok with 3.8.2, Stephan Boettcher
• compat-drivers based on v3.8.3, Luis R. Rodriguez
• [PATCH] nouveau: nv10_fence.c: avoid sparse warning, Laurent Navet
• [Bug 9576] Screen corruption at 24-bit color depth on radeon, bugzilla-daemon
• [Bug 9457] Restricting drm open file descriptors (AIGLX deadlock), bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 9457] Restricting drm open file descriptors (AIGLX deadlock), bugzilla-daemon
• [Bug 9348] Hard Lockup with Ati X600 X.Org >7.1.1 caused by libdri.so, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 9348] Hard Lockup with Ati X600 X.Org >7.1.1 caused by libdri.so, bugzilla-daemon
• [Bug 9851] Bad via entries in pci ids list both for kernel tree and drm tree., bugzilla-daemon
• [Bug 9506] r300 crash on Misfit Model 3D, bugzilla-daemon
• [Bug 5999] problems with r300 and metacity compositing manager, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 5999] problems with r300 and metacity compositing manager, bugzilla-daemon
• [Bug 9301] FreeBSD system locks up with DRI enabled on Radeon RS300, bugzilla-daemon
• [Bug 8896] X error when using off-screen rendering with DRI enabled, bugzilla-daemon
• [Bug 7111] racer: [drm:drm_lock_take] *ERROR* 3 holds heavyweight lock, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 7111] racer: [drm:drm_lock_take] *ERROR* 3 holds heavyweight lock, bugzilla-daemon
  • [Bug 7111] racer: [drm:drm_lock_take] *ERROR* 3 holds heavyweight lock, bugzilla-daemon
• [Bug 3380] Dynamically generate GL dispatch functions for PowerPC, bugzilla-daemon
• [Bug 8258] drm_handle_t isn't 64bit safe, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 8258] drm_handle_t isn't 64bit safe, bugzilla-daemon
• [Bug 7971] radeon driver unable to claim hw lock from abusive dri clients, bugzilla-daemon
• [Bug 6249] VIA ME600 + XvMC + mplayer hang, bugzilla-daemon
• [Bug 6192] System hard locks when attempting to run HQ Dragothic (3D Mark 2001SE) demo in Wine, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 6192] System hard locks when attempting to run HQ Dragothic (3D Mark 2001SE) demo in Wine, bugzilla-daemon
  • [Bug 6192] System hard locks when attempting to run HQ Dragothic (3D Mark 2001SE) demo in Wine, bugzilla-daemon
  • [Bug 6192] System hard locks when attempting to run HQ Dragothic (3D Mark 2001SE) demo in Wine, bugzilla-daemon
• [Bug 6090] Texture bitmap not displaying correctly in games similar to tuxracer for r200 based cards., bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 6090] Texture bitmap not displaying correctly in games similar to tuxracer for r200 based cards., bugzilla-daemon
  • [Bug 6090] Texture bitmap not displaying correctly in games similar to tuxracer for r200 based cards., bugzilla-daemon
• [Bug 5569] savage: glxgears only shows monochrome flicker, bugzilla-daemon
• [Bug 5531] DRI enabled freezes X when running any opengl app, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 5531] DRI enabled freezes X when running any opengl app, bugzilla-daemon
• [Bug 5477] sis_dri hangs server, causes certain apps (glxcontexts) to segfault, bugzilla-daemon
• [Bug 3267] Rendering errors running foobillard on Radeon 7500, bugzilla-daemon
• [Bug 3832] Can't use R128 and Mach64 simultaniously., bugzilla-daemon
• [PATCH 1/2] drm/radeon: add support for Richland APUs, alexdeucher
  • [PATCH 2/2] drm/radeon: add Richland pci ids, alexdeucher
  • Re: [PATCH 1/2] drm/radeon: add support for Richland APUs, Jerome Glisse
• [Bug 733] kernel total freeze switching X->fb (matrox), bugzilla-daemon
• Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
  • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
  • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
    • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Yinghai Lu
      • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Shawn Starr
      • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
        • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Yinghai Lu
          • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
            • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Yinghai Lu
        • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Daniel Vetter
          • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Chris Wilson
          • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
  • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Greg KH
    • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
      • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Greg KH
        • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Jiri Kosina
        • Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses), Daniel Vetter
          • [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)), Jiri Kosina
            • Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)), Chris Wilson
              • Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)), Jiri Kosina
                • Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)), Chris Wilson
            • Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)), Daniel Vetter
• [Bug 6409] XvMC on Intel i810, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 6409] XvMC on Intel i810, bugzilla-daemon
• [Bug 7445] AMD64+Radeon display corruption, bugzilla-daemon
• [Bug 7034] via_cmdbuf_wait timed out hw, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 7034] via_cmdbuf_wait timed out hw, bugzilla-daemon
  • [Bug 7034] via_cmdbuf_wait timed out hw, bugzilla-daemon
  • [Bug 7034] via_cmdbuf_wait timed out hw, bugzilla-daemon
  • [Bug 7034] via_cmdbuf_wait timed out hw, bugzilla-daemon
• [Bug 704] Should MACCESS be validated?, bugzilla-daemon
• [Bug 9379] drmCommandNone( fd, DRM_R128_CCE_IDLE ) - gives errno 22, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 9379] drmCommandNone( fd, DRM_R128_CCE_IDLE ) - gives errno 22, bugzilla-daemon
  • [Bug 9379] drmCommandNone( fd, DRM_R128_CCE_IDLE ) - gives errno 22, bugzilla-daemon
  • [Bug 9379] drmCommandNone( fd, DRM_R128_CCE_IDLE ) - gives errno 22, bugzilla-daemon
• [Bug 8634] [r128] Driver does not support GLX_SGI_make_current_read, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 8634] [r128] Driver does not support GLX_SGI_make_current_read, bugzilla-daemon
• [Bug 3493] r128: Entire X-windowing system hangs during normal 3D gaming, bugzilla-daemon
• [Bug 20537] piglit failures on ATI Mobility M6, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 20537] piglit failures on ATI Mobility M6, bugzilla-daemon
• [Bug 21284] [KMS] Radeon rv280 black screen with modeset=1, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 21284] [KMS] Radeon rv280 black screen with modeset=1, bugzilla-daemon
• [Bug 21122] If DRI is enabled ,System will freeze after X quit, bugzilla-daemon
• [Bug 20751] 2D acceleration on R6xx freezes my computer, bugzilla-daemon
• [Bug 20129] Large texture object obscuring display with radeon driver in dxx-rebirth, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 20129] Large texture object obscuring display with radeon driver in dxx-rebirth, bugzilla-daemon
• [Bug 20211] Runing Kubrick game maximized freezes X and causes kernel panic, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 20211] Runing Kubrick game maximized freezes X and causes kernel panic, bugzilla-daemon
  • [Bug 20211] Runing Kubrick game maximized freezes X and causes kernel panic, bugzilla-daemon
  • [Bug 20211] Runing Kubrick game maximized freezes X and causes kernel panic, bugzilla-daemon
• [PATCH v2 0/3] R-Car Display Unit DRM driver, Laurent Pinchart
  • [PATCH v2 1/3] r8a7779: Add Display Unit clock support, Laurent Pinchart
  • [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Laurent Pinchart
    • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Sergei Shtylyov
      • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Laurent Pinchart
        • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Sergei Shtylyov
          • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Laurent Pinchart
            • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Sergei Shtylyov
    • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Sergei Shtylyov
      • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Laurent Pinchart
    • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Simon Horman
      • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Laurent Pinchart
        • Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support, Simon Horman
  • [PATCH v2 2/3] drm: Renesas R-Car Display Unit DRM driver, Laurent Pinchart
• PCI Speed Cap Fixes for ppc64, lucaskt
  • [PATCH 2/2] ppc64: Add arch-specific pcie_get_speed_cap_mask, lucaskt
    • Re: [PATCH 2/2] ppc64: Add arch-specific pcie_get_speed_cap_mask, Thadeu Lima de Souza Cascardo
  • [PATCH 1/2] drm: Move drm_pcie_get_speed_cap_mask to PCI, lucaskt
    • Re: [PATCH 1/2] drm: Move drm_pcie_get_speed_cap_mask to PCI, Thadeu Lima de Souza Cascardo
• [PATCH] drm/exynos: change the method for getting the interrupt resource of FIMD, Vikas Sajjan
  • Re: [PATCH] drm/exynos: change the method for getting the interrupt resource of FIMD, Vikas Sajjan
    • Re: [PATCH] drm/exynos: change the method for getting the interrupt resource of FIMD, Inki Dae
• i915 drm oopses while fuzzing, Tommi Rantala
  • [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Chris Wilson
    • Re: [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Tommi Rantala
      • [PATCH] drm: Perform ioctl command validation on the stored kernel values, Chris Wilson
        • Re: [PATCH] drm: Perform ioctl command validation on the stored kernel values, Dave Airlie
    • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Ben Widawsky
    • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Ben Widawsky
      • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Chris Wilson
        • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Ben Widawsky
          • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Chris Wilson
            • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Ben Widawsky
              • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Chris Wilson
                • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Daniel Vetter
                  • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Chris Wilson
                    • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Dave Airlie
                      • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Chris Wilson
                        • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Tommi Rantala
                  • Re: [Intel-gfx] [PATCH] drm/i915: Sanity check incoming ioctl data for a NULL pointer, Dave Jones
• [Bug 62311] New: (kernel) memory leak, bugzilla-daemon
  • [Bug 62311] (kernel) memory leak, bugzilla-daemon
  • [Bug 62311] [r600g] (kernel) memory leak, bugzilla-daemon
  • [Bug 62311] [r600g] (kernel) memory leak, bugzilla-daemon
  • [Bug 62311] [r600g] (kernel) memory leak, bugzilla-daemon
  • [Bug 62311] [r600g] (kernel) memory leak, bugzilla-daemon
• [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2", Paul Bolle
  • Re: [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2", Paul Bolle
    • Re: [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2", Rob Clark
      • Re: [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2", Tomi Valkeinen
        • Re: [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2", Dave Airlie
  • Re: [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2", Thierry Reding
• [PATCH 1/2] drm/radeon/benchmark: make sure bo blit copy exists before using it, alexdeucher
  • [PATCH 2/2] drm/radeon/benchmark: allow same domains for dma copy, alexdeucher
    • Re: [PATCH 2/2] drm/radeon/benchmark: allow same domains for dma copy, Paul Menzel
      • Re: [PATCH 2/2] drm/radeon/benchmark: allow same domains for dma copy, Alex Deucher
  • Re: [PATCH 1/2] drm/radeon/benchmark: make sure bo blit copy exists before using it, Michel Dänzer
  • Re: [PATCH 1/2] drm/radeon/benchmark: make sure bo blit copy exists before using it, Paul Menzel
    • Re: [PATCH 1/2] drm/radeon/benchmark: make sure bo blit copy exists before using it, Alex Deucher
• Re: OOPS with 3.9.0rc2+, Borislav Petkov
  • Re: OOPS with 3.9.0rc2+, Hillf Danton
• [PATCHv7 00/10] Support for Tegra 2D hardware, Terje Bergstrom
  • [PATCHv7 06/10] drm: tegra: Move drm to live under host1x, Terje Bergstrom
  • [PATCHv7 03/10] gpu: host1x: Add syncpoint wait and interrupts, Terje Bergstrom
  • [PATCHv7 09/10] gpu: host1x: drm: Add CMA ops for host1x driver, Terje Bergstrom
  • [PATCHv7 02/10] gpu: host1x: Add host1x driver, Terje Bergstrom
  • [PATCHv7 07/10] gpu: host1x: drm: Rename host1x to host1x_drm, Terje Bergstrom
  • [PATCHv7 01/10] gpu: drm: Support CMA object preallocation, Terje Bergstrom
  • [PATCHv7 08/10] gpu: host1x: Remove second host1x driver, Terje Bergstrom
  • [PATCHv7 04/10] gpu: host1x: Add channel support, Terje Bergstrom
  • [PATCHv7 10/10] drm: tegra: Add gr2d device, Terje Bergstrom
    • Re: [PATCHv7 10/10] drm: tegra: Add gr2d device, Thierry Reding
      • Re: [PATCHv7 10/10] drm: tegra: Add gr2d device, Terje Bergström
      • Re: [PATCHv7 10/10] drm: tegra: Add gr2d device, Terje Bergström
  • [PATCHv7 05/10] gpu: host1x: Add debug support, Terje Bergstrom
• [WARNING v3.9-rc2] [nouveau] possible recursive locking detected in evo_wait(), Konstantin Khlebnikov
• [PATCH 7/7] drm/exynos: Check g2d cmd list for g2d restrictions, Inki Dae
  • [PATCH v2 7/7] drm/exynos: Check g2d cmd list for g2d restrictions, Inki Dae
• [PATCH 5/7] drm/exynos: Deal with g2d buffer info more efficiently, Inki Dae
  • [PATCH v2 5/7] drm/exynos: Deal with g2d buffer info more efficiently, Inki Dae
• [PATCH 6/7] drm/exynos: Add a new function to get gem buffer size, Inki Dae
• [PATCH 4/7] drm/exynos: Clean up some G2D codes for readability, Inki Dae
  • Re: [PATCH 4/7] drm/exynos: Clean up some G2D codes for readability, Joonyoung Shim
  • [PATCH v2 4/7] drm/exynos: Clean up some G2D codes for readability, Inki Dae
• [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Inki Dae
  • Re: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Joonyoung Shim
    • RE: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Inki Dae
      • Re: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Joonyoung Shim
        • RE: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Inki Dae
          • Re: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Joonyoung Shim
            • RE: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, Inki Dae
              • RE: [PATCH 3/7] drm/exynos: Fix G2D core mulfunctioning issue, YoungJun Cho
  • [PATCH v2 3/7] drm/exynos: Fix G2D core malfunctioning issue, Inki Dae
• [PATCH 2/7] drm/exynos: clear node object type at gem unmap, Inki Dae
• [PATCH 1/7] drm/exynos: Fix error routine to getting dma addr., Inki Dae
• [PATCH 0/7] Consider G2D hardware restrictions., Inki Dae
  • [PATCH v2 0/7] Consider G2D hardware restrictions., Inki Dae
  • Re: [PATCH 0/7] Consider G2D hardware restrictions., Rob Clark
    • Re: [PATCH 0/7] Consider G2D hardware restrictions., YoungJun Cho
      • Re: [PATCH 0/7] Consider G2D hardware restrictions., Rob Clark
        • Re: [PATCH 0/7] Consider G2D hardware restrictions., YoungJun Cho
          • Re: [PATCH 0/7] Consider G2D hardware restrictions., Rob Clark
            • Re: [PATCH 0/7] Consider G2D hardware restrictions., Inki Dae
• How to manage OMAP display drivers in the future, Tomi Valkeinen
  • Re: How to manage OMAP display drivers in the future, Rob Clark
    • Re: How to manage OMAP display drivers in the future, Tomi Valkeinen
  • Re: How to manage OMAP display drivers in the future, Tomi Valkeinen
    • Re: How to manage OMAP display drivers in the future, Laurent Pinchart
• [PATCH] DRI2: don't advertise GLX_INTEL_swap_event if it can't, Rob Clark
  • Re: [PATCH] DRI2: don't advertise GLX_INTEL_swap_event if it can't, Paul Menzel
• [PATCH 0/2] GEM CMA DMA-BUF support, Laurent Pinchart
  • [PATCH 1/2] drm: GEM CMA: Split object creation into object alloc and DMA memory alloc, Laurent Pinchart
  • [PATCH 2/2] drm: GEM CMA: Add DRM PRIME support, Laurent Pinchart
  • Re: [PATCH 0/2] GEM CMA DMA-BUF support, Laurent Pinchart
    • Re: [PATCH 0/2] GEM CMA DMA-BUF support, Laurent Pinchart
      • Re: [PATCH 0/2] GEM CMA DMA-BUF support, Laurent Pinchart
        • Re: [PATCH 0/2] GEM CMA DMA-BUF support, Rob Clark
          • Re: [PATCH 0/2] GEM CMA DMA-BUF support, Laurent Pinchart
• [PATCH] drm/shmobile: Fix race condition between page flip request and handler, Laurent Pinchart
  • Re: [PATCH] drm/shmobile: Fix race condition between page flip request and handler, Laurent Pinchart
    • Re: [PATCH] drm/shmobile: Fix race condition between page flip request and handler, Laurent Pinchart
• [PATCH] drm: Destroy property blobs at mode config cleanup time, Laurent Pinchart
  • Re: [PATCH] drm: Destroy property blobs at mode config cleanup time, Daniel Vetter
    • Re: [PATCH] drm: Destroy property blobs at mode config cleanup time, Laurent Pinchart
• [Bug 62246] New: LVDS screen mode switching fails, bugzilla-daemon
  • [Bug 62246] LVDS screen mode switching fails, bugzilla-daemon
  • [Bug 62246] LVDS screen mode switching fails, bugzilla-daemon
  • [Bug 62246] LVDS screen mode switching fails, bugzilla-daemon
• [Bug 62244] New: SIGFPE with cogl GL client in wayland, bugzilla-daemon
  • [Bug 62244] SIGFPE with cogl GL client in wayland, bugzilla-daemon
  • [Bug 62244] SIGFPE with cogl GL client in wayland, bugzilla-daemon
  • [Bug 62244] SIGFPE with cogl GL client in wayland, bugzilla-daemon
• Re: Who is responsible for radeon driver bugs?, Borislav Petkov
  • Re: Who is responsible for radeon driver bugs?, Alex Deucher
• [Bug 62239] New: radeon drm oops with benchmark=1 on Radeon 7950, bugzilla-daemon
  • [Bug 62239] radeon drm oops with benchmark=1 on Radeon 7950, bugzilla-daemon
  • [Bug 62239] radeon drm oops with benchmark=1 on Radeon 7950, bugzilla-daemon
  • [Bug 62239] radeon drm oops with benchmark=1 on Radeon 7950, bugzilla-daemon
  • [Bug 62239] radeon drm oops with benchmark=1 on Radeon 7950, bugzilla-daemon
• [Bug 62226] New: Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
  • [Bug 62226] Build Fails with LLVM, bugzilla-daemon
• [PATCH 1/5] videomode: simplify videomode Kconfig and Makefile, Tomi Valkeinen
  • [PATCH 2/5] videomode: combine videomode dmt_flags and data_flags, Tomi Valkeinen
  • [PATCH 3/5] videomode: create enum for videomode's display flags, Tomi Valkeinen
  • [PATCH 5/5] videomode: rename fields, Tomi Valkeinen
    • Re: [PATCH 5/5] videomode: rename fields, Laurent Pinchart
      • Re: [PATCH 5/5] videomode: rename fields, Tomi Valkeinen
        • Re: [PATCH 5/5] videomode: rename fields, Daniel Vetter
          • Re: [PATCH 5/5] videomode: rename fields, Tomi Valkeinen
    • Re: [PATCH 5/5] videomode: rename fields, Steffen Trumtrar
  • [PATCH 4/5] videomode: remove timing_entry_index, Tomi Valkeinen
  • Re: [PATCH 1/5] videomode: simplify videomode Kconfig and Makefile, Laurent Pinchart
• [PATCH] drm: Fix two memleaks., majianpeng
  • Re: [PATCH] drm: Fix two memleaks., Chris Wilson
• [PATCH] drm/i915: use do_div() as needed in debugfs code, Kees Cook
  • Re: [PATCH] drm/i915: use do_div() as needed in debugfs code, Daniel Vetter
• [PATCH 06/18] driver: gpu: drm: i915: remove cast for kzalloc return value, Zhang Yanfei
• [PATCH v3] drm/i915: bounds check execbuffer relocation count, Kees Cook
  • Re: [PATCH v3] drm/i915: bounds check execbuffer relocation count, Chris Wilson
    • Re: [PATCH v3] drm/i915: bounds check execbuffer relocation count, Daniel Vetter
      • Re: [PATCH v3] drm/i915: bounds check execbuffer relocation count, Daniel Vetter
        • Re: [PATCH v3] drm/i915: bounds check execbuffer relocation count, Kees Cook
          • Re: [Intel-gfx] [PATCH v3] drm/i915: bounds check execbuffer relocation count, Damien Lespiau
• sub function power management (gpu + audio device), Dave Airlie
  • Re: sub function power management (gpu + audio device), Takashi Iwai
• linux-next: build failure after merge of the final tree (drm-intel tree related), Stephen Rothwell
  • Re: linux-next: build failure after merge of the final tree (drm-intel tree related), Kees Cook
    • Re: linux-next: build failure after merge of the final tree (drm-intel tree related), Sedat Dilek
      • Re: linux-next: build failure after merge of the final tree (drm-intel tree related), Sedat Dilek
  • Re: linux-next: build failure after merge of the final tree (drm-intel tree related), Daniel Vetter
• [PATCH] drm/radeon: fix backend map setup on 1 RB trinity boards, alexdeucher
• [PATCH v2] drm/i915: clarify reasoning for the access_ok call, Kees Cook
  • Re: [PATCH v2] drm/i915: clarify reasoning for the access_ok call, Daniel Vetter
• [PATCH v2] drm/i915: bounds check execbuffer relocation count, Kees Cook
  • Re: [PATCH v2] drm/i915: bounds check execbuffer relocation count, Chris Wilson
    • Re: [PATCH v2] drm/i915: bounds check execbuffer relocation count, Kees Cook
      • Re: [PATCH v2] drm/i915: bounds check execbuffer relocation count, Chris Wilson
• [PATCH REPOST] drm: tegra: don't depend on OF, Stephen Warren
  • Re: [PATCH REPOST] drm: tegra: don't depend on OF, Thierry Reding
• [PATCH 0/2] Properly suspend/resume sub-allocator, alexdeucher
  • [PATCH 1/2] drm/radeon: fix S/R on VM systems (cayman/TN/SI), alexdeucher
    • Re: [PATCH 1/2] drm/radeon: fix S/R on VM systems (cayman/TN/SI), Christian König
  • [PATCH 2/2] drm/radeon: tear down the IB pool on suspend, alexdeucher
    • Re: [PATCH 2/2] drm/radeon: tear down the IB pool on suspend, Christian König
• [PATCH] drivers: gpu: drm: gma500: Replaced calls kzalloc & memcpy with kmemdup, Alexandru Gheorghiu
  • Re: [PATCH] drivers: gpu: drm: gma500: Replaced calls kzalloc & memcpy with kmemdup, Patrik Jakobsson
  • Re: [PATCH] drivers: gpu: drm: gma500: Replaced calls kzalloc & memcpy with kmemdup, Patrik Jakobsson
• [PATCH] drivers: gpu: drm: Replaced ERR_PTR & PTR_ERR with ERR_CAST, Alexandru Gheorghiu
• [PATCH] drivers: gpu: drm: i915: Replaced calls to kmalloc & memcpy with kmemdup, Alexandru Gheorghiu
  • Re: [PATCH] drivers: gpu: drm: i915: Replaced calls to kmalloc & memcpy with kmemdup, Josh Triplett
    • Re: [PATCH] drivers: gpu: drm: i915: Replaced calls to kmalloc & memcpy with kmemdup, Andru Gheorghiu
  • <Possible follow-ups>
  • [PATCH] drivers: gpu: drm: i915: Replaced calls to kmalloc & memcpy with kmemdup, Alexandru Gheorghiu
    • Re: [PATCH] drivers: gpu: drm: i915: Replaced calls to kmalloc & memcpy with kmemdup, Joe Perches
• [PATCH] drm/i915: bounds check execbuffer relocations, Kees Cook
  • Re: [PATCH] drm/i915: bounds check execbuffer relocations, Chris Wilson
    • Re: [PATCH] drm/i915: bounds check execbuffer relocations, Kees Cook
• [PATCH] drm/radeon: check incoming cliprects pointer, Kees Cook
• [PATCH] drm/i915: clarify reasoning for the access_ok call, Kees Cook
  • Re: [PATCH] drm/i915: clarify reasoning for the access_ok call, Chris Wilson
    • Re: [PATCH] drm/i915: clarify reasoning for the access_ok call, Kees Cook
      • Re: [PATCH] drm/i915: clarify reasoning for the access_ok call, Chris Wilson
• [PATCH] drivers: gpu: drm: exynos: Replaced kzalloc & memcpy with kmemdup, Alexandru Gheorghiu
  • Re: [PATCH] drivers: gpu: drm: exynos: Replaced kzalloc & memcpy with kmemdup, 김승우
  • Re: [PATCH] drivers: gpu: drm: exynos: Replaced kzalloc & memcpy with kmemdup, Inki Dae
• [PATCH] drm/i915: restrict kernel address leak in debugfs, Kees Cook
  • Re: [PATCH] drm/i915: restrict kernel address leak in debugfs, Daniel Vetter
• [PATCH V3] get_maintainer: use filename-only regex match for Tegra, Stephen Warren
  • Re: [PATCH V3] get_maintainer: use filename-only regex match for Tegra, Joe Perches
  • Re: [PATCH V3] get_maintainer: use filename-only regex match for Tegra, Marcin Ślusarz
    • Re: [PATCH V3] get_maintainer: use filename-only regex match for Tegra, Stephen Warren
• [Bug 62170] New: [bisected] R600 LLVM build broken, bugzilla-daemon
  • [Bug 62170] [bisected] R600 LLVM build broken, bugzilla-daemon
  • [Bug 62170] [bisected] R600 LLVM build broken, bugzilla-daemon
• [PATCH] drm/i915: use simple attribute in debugfs routines, Kees Cook
  • Re: [PATCH] drm/i915: use simple attribute in debugfs routines, Daniel Vetter
    • Re: [PATCH] drm/i915: use simple attribute in debugfs routines, Kees Cook
• [PATCH] make 'vmw_fence_obj_add_action' static, Ghennadi Procopciuc
• [PATCH] make 'vmw_fences_perform_actions' static, Ghennadi Procopciuc
• [PATCH] gpu: make 'vmw_event_fence_action_create' static, Ghennadi Procopciuc
• [PATCH] gpu: don't cast kzalloc() return value, Mihnea Dobrescu-Balaur
  • Re: [PATCH] gpu: don't cast kzalloc() return value, Daniel Vetter
• [PATCH] drivers/gpu/drm/tilcdc: Makefile, only -Werror when no -W* in EXTRA_CFLAGS, Chen Gang
  • Re: [PATCH] drivers/gpu/drm/tilcdc: Makefile, only -Werror when no -W* in EXTRA_CFLAGS, Rob Clark
    • Re: [PATCH] drivers/gpu/drm/tilcdc: Makefile, only -Werror when no -W* in EXTRA_CFLAGS, Chen Gang
• linux 3.9-rc1: nouveau crash on PPC, Aaro Koskinen
  • Re: linux 3.9-rc1: nouveau crash on PPC, Aaro Koskinen
• [Suggestion] drivers/gpu/drm/tilcdc: link failed, Chen Gang
  • Re: [Suggestion] drivers/gpu/drm/tilcdc: link failed, Chen Gang
• [PATCH] drivers/gpu/drm/omapdrm: Makefile, only -Werror when no -W* in EXTRA_CFLAGS, Chen Gang
  • Re: [PATCH] drivers/gpu/drm/omapdrm: Makefile, only -Werror when no -W* in EXTRA_CFLAGS, Rob Clark
• [PATCH v2 03/20] x86, ACPI, mm: Kill max_low_pfn_mapped, Yinghai Lu
  • Re: [PATCH v2 03/20] x86, ACPI, mm: Kill max_low_pfn_mapped, Tejun Heo
    • Re: [PATCH v2 03/20] x86, ACPI, mm: Kill max_low_pfn_mapped, Yinghai Lu
• [PATCH v13 0/2] Add display-timing node parsing to exynos drm fimd, Vikas Sajjan
  • [PATCH v13 1/2] video: drm: exynos: Add display-timing node parsing using video helper function, Vikas Sajjan
  • [PATCH v13 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd, Vikas Sajjan
• [PATCHv6 0/9] Support for Tegra 2D hardware, Terje Bergstrom
  • [PATCHv6 6/9] gpu: host1x: drm: Rename host1x to host1x_drm, Terje Bergstrom
  • [PATCHv6 5/9] drm: tegra: Move drm to live under host1x, Terje Bergstrom
  • [PATCHv6 4/9] gpu: host1x: Add debug support, Terje Bergstrom
  • [PATCHv6 2/9] gpu: host1x: Add syncpoint wait and interrupts, Terje Bergstrom
  • [PATCHv6 3/9] gpu: host1x: Add channel support, Terje Bergstrom
  • [PATCHv6 9/9] drm: tegra: Add gr2d device, Terje Bergstrom
  • [PATCHv6 7/9] gpu: host1x: Remove second host1x driver, Terje Bergstrom
  • [PATCHv6 8/9] gpu: host1x: drm: Add CMA ops for host1x driver, Terje Bergstrom
  • [PATCHv6 1/9] gpu: host1x: Add host1x driver, Terje Bergstrom
• [Bug 62012] New: Intermittent black geometry, bugzilla-daemon
  • [Bug 62012] Intermittent black geometry, bugzilla-daemon
• [PATCH V4] drm/exynos: fimd: calculate the correct address offset, Leela Krishna Amudala
• [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Yinghai Lu
  • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Tejun Heo
    • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Yinghai Lu
      • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Tejun Heo
        • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Yinghai Lu
          • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Tejun Heo
            • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, H. Peter Anvin
              • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Daniel Vetter
                • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, Chris Wilson
                • Re: [PATCH 01/14] x86, ACPI, mm: Kill max_low_pfn_mapped, H. Peter Anvin
• [pull] radeon drm-fixes-3.9, alexdeucher
  • <Possible follow-ups>
  • [pull] radeon drm-fixes-3.9, alexdeucher
• [Bug 61979] backlight adjustment doesn't work on HP Pavilion m6-1035dx, bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 61979] backlight adjustment doesn't work on HP Pavilion m6-1035dx, bugzilla-daemon
• [PATCH] drm: call drm_device_set_unplugged in drm_put_dev, Maarten Lankhorst
• Wrong vsync offset calculation in drm_edid.c, Peter Blum
  • Re: Wrong vsync offset calculation in drm_edid.c, Paul Menzel
• [PATCH 0/2] mgag200 fix plus documentation typo fixes, Christopher Harvey
  • [PATCH 2/2] drm: Documentation typo fixes, Christopher Harvey
  • [PATCH 1/2] drm/mgag200: Bug fix: Renesas board now selects native resolution., Julia Lemire
• Black screen with nouveau in 3.8.x (regression), Nick Bowler
  • Re: Black screen with nouveau in 3.8.x (regression), Nick Bowler
  • Re: Black screen with nouveau in 3.8.x (regression), Nick Bowler
• [PATCH V3] drm/exynos: fimd: calculate the correct address offset, Leela Krishna Amudala
  • Re: [PATCH V3] drm/exynos: fimd: calculate the correct address offset, Joonyoung Shim
• [PATCH v12 0/2] Add display-timing node parsing to exynos drm fimd, Vikas Sajjan
  • [PATCH v12 1/2] video: drm: exynos: Add display-timing node parsing using video helper function, Vikas Sajjan
  • [PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd, Vikas Sajjan
    • RE: [PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd, Inki Dae
      • Re: [PATCH v12 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd, Vikas Sajjan
• [PATCH v11 0/2] Add display-timing node parsing to exynos drm fimd, Vikas Sajjan
  • [PATCH v11 1/2] video: drm: exynos: Add display-timing node parsing using video helper function, Vikas Sajjan
  • [PATCH v11 2/2] drm/exynos: enable OF_VIDEOMODE and FB_MODE_HELPERS for exynos drm fimd, Vikas Sajjan
• [Bug 61965] New: Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium, bugzilla-daemon
  • [Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium, bugzilla-daemon
  • [Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium, bugzilla-daemon
  • [Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium, bugzilla-daemon
  • [Bug 61965] Kernel panics drm_fb_helper_restore_fbdev_mode when using Chromium, bugzilla-daemon
• [PATCH V2 1/3] get_maintainer: create filename-only regex match type, Stephen Warren
  • [PATCH V2 2/3] MAINTAINERS: tegra: match related files using N: not K:, Stephen Warren
  • [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames, Stephen Warren
    • Re: [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames, Joe Perches
      • Re: [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames, Stephen Warren
        • Re: [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames, Joe Perches
          • Re: [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames, Stephen Warren
            • Re: [PATCH V2 3/3] get_maintainer: prevent keywords from matching filenames, Joe Perches
• [PATCH 1/2] get_maintainer: create filename-only regex match type, Stephen Warren
  • [PATCH 2/2] MAINTAINERS: tegra: match related files using N: not K:, Stephen Warren
  • Re: [PATCH 1/2] get_maintainer: create filename-only regex match type, Joe Perches
• [Bug 61529] [ATI RV710] r600_pcie_gart_tlb_flush+0xf5/0x110, bugzilla-daemon
• qemu qxl kms driver, Dave Airlie
  • [PATCH 1/2] ttm: export functions to allow qxl do its own iomapping, Dave Airlie
  • [PATCH 2/2] drm: add new QXL driver., Dave Airlie
• [PATCH V2] drm/exynos: fimd: calculate the correct address offset, Leela Krishna Amudala
  • Re: [PATCH V2] drm/exynos: fimd: calculate the correct address offset, Joonyoung Shim
  • Re: [PATCH V2] drm/exynos: fimd: calculate the correct address offset, Paul Menzel
• [PATCH] drm: fix new kernel-doc warnings, Randy Dunlap
  • Re: [PATCH] drm: fix new kernel-doc warnings, Rob Landley
• v3.9-rc1 instability on Chromebook Pixel with gmbus irq, Benson Leung
  • Re: v3.9-rc1 instability on Chromebook Pixel with gmbus irq, Daniel Vetter
    • Re: v3.9-rc1 instability on Chromebook Pixel with gmbus irq, Jani Nikula
    • Re: v3.9-rc1 instability on Chromebook Pixel with gmbus irq, Benson Leung
• [Bug 61883] New: wine shader_generate_glsl_declarations fail, bugzilla-daemon
  • [Bug 61883] wine shader_generate_glsl_declarations fail, bugzilla-daemon
  • [Bug 61883] wine shader_generate_glsl_declarations fail, bugzilla-daemon
  • [Bug 61883] wine shader_generate_glsl_declarations fail, bugzilla-daemon
• [PATCH] drm/tegra: drop "select DRM_HDMI", Paul Bolle
  • Re: [PATCH] drm/tegra: drop "select DRM_HDMI", Thierry Reding
• nouveau bug in 3.7.9 -- unable to handle kernel paging request, Ilia Mirkin
• [PATCH 0/4] drm/omap: Misc fixes and improvements, Archit Taneja
  • [PATCH 1/4] drm/omap: Don't return from modeset_init if a panel doesn't satisfy omapdrm requirements, Archit Taneja
    • Re: [PATCH 1/4] drm/omap: Don't return from modeset_init if a panel doesn't satisfy omapdrm requirements, Rob Clark
  • [PATCH 3/4] drm/omap: Make fixed resolution panels work, Archit Taneja
    • Re: [PATCH 3/4] drm/omap: Make fixed resolution panels work, Rob Clark
      • Re: [PATCH 3/4] drm/omap: Make fixed resolution panels work, Archit Taneja
  • [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Archit Taneja
    • Re: [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Tomi Valkeinen
      • Re: [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Archit Taneja
        • Re: [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Tomi Valkeinen
          • Re: [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Archit Taneja
            • Re: [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Tomi Valkeinen
              • Re: [PATCH 4/4] omapdss: features: fixed supported outputs for OMAP4, Archit Taneja