Re: [Intel-gfx] [PATCH 3/3] intel: Add a function for the new register read ioctl.

2012-08-02 Thread Ben Widawsky
On 2012-08-02 11:29, Eric Anholt wrote: --- I'm not sure if this is the API we want or not. Getting your value back through an out parameter sucks. On the other hand, the 3d driver wants to be able to use the error value to detect a supported kernel. My other API thought would be for reg_rea

Re: [Intel-gfx] [PATCH 2/3] intel: Import updated i915_drm.h.

2012-08-02 Thread Ben Widawsky
On 2012-08-02 11:29, Eric Anholt wrote: Yikes, who spelled caching wrong? Reviewed-by: Ben Widawsky --- include/drm/i915_drm.h | 33 - 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/include/drm/i915_drm.h b/include/drm/i915_drm.h index 5c8fabe.

Re: [Intel-gfx] [PATCH 1/3] Drop "-Wunsafe-loop-optimizations".

2012-08-02 Thread Ben Widawsky
On 2012-08-02 11:29, Eric Anholt wrote: It warns about totally sensible things done in intel_decode.c. I've never seen this warn do anything useful, and apparently I was the one to introduce it when I added the giant pile of warning flags back in 2008. --- configure.ac |2 +- 1 file changed

[Intel-gfx] [PATCH 3/3] intel: Add a function for the new register read ioctl.

2012-08-02 Thread Eric Anholt
--- I'm not sure if this is the API we want or not. Getting your value back through an out parameter sucks. On the other hand, the 3d driver wants to be able to use the error value to detect a supported kernel. My other API thought would be for reg_read() to return the value and whine if an erro

[Intel-gfx] [PATCH 2/3] intel: Import updated i915_drm.h.

2012-08-02 Thread Eric Anholt
--- include/drm/i915_drm.h | 33 - 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/include/drm/i915_drm.h b/include/drm/i915_drm.h index 5c8fabe..7e9e9bd 100644 --- a/include/drm/i915_drm.h +++ b/include/drm/i915_drm.h @@ -195,6 +195,9 @@ typedef str

[Intel-gfx] [PATCH 1/3] Drop "-Wunsafe-loop-optimizations".

2012-08-02 Thread Eric Anholt
It warns about totally sensible things done in intel_decode.c. I've never seen this warn do anything useful, and apparently I was the one to introduce it when I added the giant pile of warning flags back in 2008. --- configure.ac |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --gi

Re: [Intel-gfx] [PATCH intel-gpu-tools] tools: Added intel_dpio_read and intel_dpio_write

2012-08-02 Thread Ben Widawsky
On 2012-08-02 05:07, Vijay Purushothaman wrote: In Valleyview the DPLL and lane control registers are accessible only through side band fabric called DPIO. Added two tools to read and write registers residing in this space. Could I convince you to use the centralized read/write mmio functions

[Intel-gfx] [PATCH intel-gpu-tools] tools: Added intel_dpio_read and intel_dpio_write

2012-08-02 Thread Vijay Purushothaman
In Valleyview the DPLL and lane control registers are accessible only through side band fabric called DPIO. Added two tools to read and write registers residing in this space. Signed-off-by: Vijay Purushothaman --- tools/Makefile.am|2 + tools/intel_dpio_read.c | 105 ++

[Intel-gfx] 2012-07-24: Intel® 12.07 graphics package released.

2012-08-02 Thread Виктор
Hello Team! I saw that Intel package released, I have i7 CPU with internal HD 4000 graphics chip and use now "vesa" driver with Mandriva linux, because no others worked. I update kernel to 3.4.4 (if I right, not remember exactly version, but it 3.4.x).  As I understood 12.07 package support H