Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix color order for BGR formats on SNB

2012-03-07 Thread Jesse Barnes
Dave, not sure if Keith has setup his -fixes tree again, but this one needs to go to Linus in your next pull assuming you're doing one. Otherwise we can just send it to stable after 3.3 is out. I have one more similar fix for the i915 fb init code that was preventing us from using BGR formats (a

Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix color order for BGR formats on SNB

2012-03-07 Thread Keith Packard
#part sign=pgpmime On Wed, 7 Mar 2012 07:02:02 -0800, Jesse Barnes jbar...@virtuousgeek.org wrote: Dave, not sure if Keith has setup his -fixes tree again, but this one needs to go to Linus in your next pull assuming you're doing one. Yeah, I got home just in time to travel for a whole week.

Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix color order for BGR formats on SNB

2012-03-07 Thread Keith Packard
#part sign=pgpmime On Mon, 27 Feb 2012 12:40:10 -0800, Jesse Barnes jbar...@virtuousgeek.org wrote: Had the wrong bits and field definitions. Merged. 617cf88..ab2f9df drm-intel-fixes - drm-intel-fixes -- keith.pack...@intel.com ___ Intel-gfx

Re: [Intel-gfx] [PATCH] drm/i915: support 32 bit BGR formats in sprite planes

2012-03-07 Thread Keith Packard
#part sign=pgpmime On Wed, 7 Mar 2012 08:49:29 -0800, Jesse Barnes jbar...@virtuousgeek.org wrote: intel_framebuffer_init does some basic sanity checking of the pixel format, but is used by the plane code in addition to the primary crtc. So it needs to contain any formats used in either

[Intel-gfx] [PATCH 2/2] intel: Add .aub file output support.

2012-03-07 Thread Eric Anholt
From: Kenneth Graunke kenn...@whitecape.org This will allow the driver to capture all of its execution state to a file for later debugging. intel_gpu_dump is limited in that it only captures batchbuffers, and Mesa's captures, while more complete, still capture only a portion of the state

[Intel-gfx] [PATCH 1/2] intel: Add support for overriding the PCI ID via an environment variable

2012-03-07 Thread Eric Anholt
From: Kenneth Graunke kenn...@whitecape.org For example: export INTEL_DEVID_OVERRIDE=0x162 If this variable is set, don't actually submit the batchbuffer to the GPU, it probably contains commands for the wrong generation of hardware. v2: Introduce a getter for the overridden devid, and

Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix color order for BGR formats on SNB

2012-03-07 Thread Jesse Barnes
Keith Packard kei...@keithp.com wrote: #part sign=pgpmime On Wed, 7 Mar 2012 07:02:02 -0800, Jesse Barnes jbar...@virtuousgeek.org wrote: Dave, not sure if Keith has setup his -fixes tree again, but this one needs to go to Linus in your next pull assuming you're doing one. Yeah, I got home

Re: [Intel-gfx] [PATCH 1/2] drm/i915: fix color order for BGR formats on SNB

2012-03-07 Thread Keith Packard
#part sign=pgpmime On Wed, 07 Mar 2012 14:04:28 -0800, Jesse Barnes jbar...@virtuousgeek.org wrote: Yeah, only 1/2 belongs in fixes. The other one needs another patch on top to avoid unpinning an active buffer. Hence 'sketchy' :-) -- keith.pack...@intel.com

Re: [Intel-gfx] [PATCH] intel: Fix a case when mapping large texture fails

2012-03-07 Thread Anuj Phogat
On Mon 27 Feb 2012 11:45:46 AM PST, Anuj Phogat wrote: This patch handles a case when mapping a large texture fails in drm_intel_gem_bo_map_gtt(). These changes avoid assertion failure later in the driver as reported in following bugs: https://bugs.freedesktop.org/show_bug.cgi?id=44970

Re: [Intel-gfx] [PATCH 1/2] intel: Add support for overriding the PCI ID via an environment variable

2012-03-07 Thread Yuanhan Liu
On Wed, Mar 07, 2012 at 11:21:06AM -0800, Eric Anholt wrote: From: Kenneth Graunke kenn...@whitecape.org For example: export INTEL_DEVID_OVERRIDE=0x162 If this variable is set, don't actually submit the batchbuffer to the GPU, it probably contains commands for the wrong generation

Re: [Intel-gfx] [PATCH 2/2] intel: Add .aub file output support.

2012-03-07 Thread Yuanhan Liu
On Wed, Mar 07, 2012 at 11:21:07AM -0800, Eric Anholt wrote: From: Kenneth Graunke kenn...@whitecape.org This will allow the driver to capture all of its execution state to a file for later debugging. intel_gpu_dump is limited in that it only captures batchbuffers, and Mesa's captures,