[3.2.y] drm/i915: add Ivy Bridge GT2 Server entries

Hi Ben, Please consider cc22a938fc1d drm/i915: add Ivy Bridge GT2 Server entries, 2012-03-29 for application to the 3.2.y tree. It adds a PCI id to the i915 driver, making kms work. It was applied during the 3.4-rc2 cycle, so newer stable kernels don't need it. Maik Zumstrull tried it[1] on

[3.2.y] drm/i915: add Ivy Bridge GT2 Server entries

Maik Zumstrull wrote: > On Sun, Oct 7, 2012 at 7:26 PM, Julien Cristau wrote: >> On Mon, Oct 1, 2012 at 03:24:32 -0700, Jonathan Nieder wrote: >>> - without this patch, modern X errors out instead of starting, [...] >> I'd expect X to start with vesa or fb

[3.0.y, 3.2.y, 3.4.y] Please add LVDS patch for the Zotac ZBOX SD ID13

Hi Ben and Greg, Please consider 9756fe38d10b drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13 for application to the 3.0.y, 3.2.y, and 3.4.y trees. It was applied upstream during the 3.6 merge window, so newer kernels don't need it. Alexander Kurtz writes, using a kernel closely based o

[3.2.y] drm/i915: add Ivy Bridge GT2 Server entries

Hi Ben, Please consider cc22a938fc1d drm/i915: add Ivy Bridge GT2 Server entries, 2012-03-29 for application to the 3.2.y tree. It adds a PCI id to the i915 driver, making kms work. It was applied during the 3.4-rc2 cycle, so newer stable kernels don't need it. Maik Zumstrull tried it[1] on

Re: [3.2.y] drm/i915: add Ivy Bridge GT2 Server entries

Maik Zumstrull wrote: > On Sun, Oct 7, 2012 at 7:26 PM, Julien Cristau wrote: >> On Mon, Oct 1, 2012 at 03:24:32 -0700, Jonathan Nieder wrote: >>> - without this patch, modern X errors out instead of starting, [...] >> I'd expect X to start with vesa or fb

Re: [3.0.y, 3.2.y, 3.4.y] Please add LVDS patch for the Zotac ZBOX SD ID13

Hi Ben and Greg, Please consider 9756fe38d10b drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13 for application to the 3.0.y, 3.2.y, and 3.4.y trees. It was applied upstream during the 3.6 merge window, so newer kernels don't need it. Alexander Kurtz writes, using a kernel closely based o

Re: [PATCH 1/2] drm/nouveau: Add lock on drm_helper_resume_force_mode

Hi, Peter Huewe wrote: > mode_config should be locked when calling drm_helper_resume_force_mode. > This patch adds the lock, similar to #927a2f119. Does this fix a problem that has been observed in the wild, or only a theoretical one? Curious, Jonathan __

Re: [PATCH] drm/kms: driver for virtual cirrus under qemu

Hi Dave, Dave Airlie wrote: > --- /dev/null > +++ b/drivers/gpu/drm/cirrus/Kconfig > @@ -0,0 +1,7 @@ > +config DRM_CIRRUS > + tristate "Cirrus driver" > + depends on DRM && PCI > + select FB_CFB_FILLRECT > + select FB_CFB_COPYAREA > + select FB_CFB_IMAGEBLIT > + select DRM

[3.4.y, 3.5.y] drm/i915: Use the correct size of the GTT for placing the per-process entries

Hi Greg, Please consider 9a0f938bde74 drm/i915: Use the correct size of the GTT for placing the per-process entries, 2012-08-24 for application to the 3.4.y tree. Without this patch, Geoff Crompton's iMac hits a BUG during bootup. The problem is reproducible on * Debian's 3.2.y

Re: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

44 57 6...6QDW > <3>30 37 32 34 36 30 38 36 37 0a 00 00 00 fd 00 32 072460867..2 > <3>4b 1e 52 11 00 0a 20 20 20 20 20 20 00 00 00 fc K.R... > <3>00 56 47 32 30 32 31 77 6d 2d 32 0a 20 20 00 64 .VG2021wm-2. .d > > And so I can't go more

[PATCH 1/2] drm/nouveau: Add lock on drm_helper_resume_force_mode

Hi, Peter Huewe wrote: > mode_config should be locked when calling drm_helper_resume_force_mode. > This patch adds the lock, similar to #927a2f119. Does this fix a problem that has been observed in the wild, or only a theoretical one? Curious, Jonathan

every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

51 44 57 6...6QDW > <3>30 37 32 34 36 30 38 36 37 0a 00 00 00 fd 00 32 072460867..2 > <3>4b 1e 52 11 00 0a 20 20 20 20 20 20 00 00 00 fc K.R... > <3>00 56 47 32 30 32 31 77 6d 2d 32 0a 20 20 00 64 .VG2021wm-2. .d > > And so I can

[3.4.y, 3.5.y] drm/i915: Use the correct size of the GTT for placing the per-process entries

Hi Greg, Please consider 9a0f938bde74 drm/i915: Use the correct size of the GTT for placing the per-process entries, 2012-08-24 for application to the 3.4.y tree. Without this patch, Geoff Crompton's iMac hits a BUG during bootup. The problem is reproducible on * Debian's 3.2.y

[PATCH] drm/kms: driver for virtual cirrus under qemu

Hi Dave, Dave Airlie wrote: > --- /dev/null > +++ b/drivers/gpu/drm/cirrus/Kconfig > @@ -0,0 +1,7 @@ > +config DRM_CIRRUS > + tristate "Cirrus driver" > + depends on DRM && PCI > + select FB_CFB_FILLRECT > + select FB_CFB_COPYAREA > + select FB_CFB_IMAGEBLIT > + select DRM