On 7/24/2014 7:46 PM, rafael.barba...@intel.com wrote:
From: Rafael Barbalho rafael.barba...@intel.com
This particular nasty presented itself while trying to register the
intelfb device (intel_fbdev.c). During the process of registering the device
the driver will disable the crtc via
On Thu, Jul 24, 2014 at 04:42:55PM +0100, John Harrison wrote:
On 23/07/2014 19:50, Daniel Vetter wrote:
On Wed, Jul 23, 2014 at 5:37 PM, John Harrison
john.c.harri...@intel.com wrote:
diff --git a/drivers/gpu/drm/i915/i915_drv.h
b/drivers/gpu/drm/i915/i915_drv.h
index 0977653..fbafa68
On Thu, Jul 24, 2014 at 01:28:21PM -0700, Jesse Barnes wrote:
If that won't work, you could just use a timer, or tie into some other
event that happens when the GPU is busy (e.g. execbuf or retire) instead
of trying to tie into the display side of things.
Yes, tying into a normal timer is
On Fri, Jul 25, 2014 at 01:28:48PM +1000, Dave Airlie wrote:
On 23 July 2014 15:11, Daniel Vetter dan...@ffwll.ch wrote:
On Sat, Jul 12, 2014 at 10:02:27AM +0530, sagar.a.kam...@intel.com wrote:
From: Borun Fu borun...@intel.com
On VLV, after i915_pm_suspend display power wells are
On Thu, Jul 24, 2014 at 05:49:29PM -0700, Matt Roper wrote:
On Wed, Jul 23, 2014 at 10:32:43PM +0200, Daniel Vetter wrote:
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index 1b5ee83ec849..4866d59b5619 100644
--- a/NEWS
+++ b/NEWS
@@ -10,6
On Thu, Jul 24, 2014 at 02:54:27PM +0100, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
commit 745945546f7366a413a3a51a37f90caa3a227b1d
breaks the build under Android because some of the
macros used in pm_rps.c are defined in sys/wait.h
which is not included.
Signed-off-by:
Try four, now including CC lists for the intel driver...
---
Hi again,
Playing some more with the new kernel release i noticed this:
[ 9064.008821] WARNING: CPU: 3 PID: 22929 at
drivers/gpu/drm/i915/intel_pm.c:5997 intel_display_power_put+0x12d/0x160()
[ 9064.008822] Modules linked in: uas
I'm pretty sure that it can be done because it is already worked on
the fedora 20. Infact I have already installed the graphic installer
and I have activated two monitors simultaneously. Now I would like to
do the same on Ubuntu 14.04. Actually I get the errors that you see on
the screenshots
On Thu, Jul 24, 2014 at 01:28:44PM +0100, Chris Wilson wrote:
Move the code around in order to acquire and release the spinlock in the
same function and in the same block. This keeps static analysers happy
and the reader sane.
Suggested-by: Julia Lawall julia.law...@lip6.fr
Signed-off-by:
On Thu, Jul 24, 2014 at 03:16:12PM +0100, rafael.barba...@intel.com wrote:
From: Rafael Barbalho rafael.barba...@intel.com
This particular nasty presented itself while trying to register the
intelfb device (intel_fbdev.c). During the process of registering the device
the driver will disable
On Fri, Jul 25, 2014 at 09:47:06AM +0200, Daniel Vetter wrote:
On Thu, Jul 24, 2014 at 03:16:12PM +0100, rafael.barba...@intel.com wrote:
From: Rafael Barbalho rafael.barba...@intel.com
This particular nasty presented itself while trying to register the
intelfb device (intel_fbdev.c).
On Thu, Jul 24, 2014 at 05:04:09PM +0100, Thomas Daniel wrote:
From: Oscar Mateo oscar.ma...@intel.com
In this patch:
commit 78382593e921c88371abd019aca8978db3248a8f
Author: Oscar Mateo oscar.ma...@intel.com
Date: Thu Jul 3 16:28:05 2014 +0100
drm/i915: Extract the actual
Hi all,
We're pleased to announce an update to Intel Graphics Virtualization Technology
(Intel GVT-g, formerly known as XenGT). Intel GVT-g is a complete vGPU solution
with mediated pass-through, supported today on 4th generation Intel Core(TM)
processors with Intel Graphics processors. A
Please format mails to a width of 75 chars or so. Decent mailers should do
that for you when hitting send.
On Thu, Jul 24, 2014 at 05:04:08PM +0100, Thomas Daniel wrote:
From: Thomas Daniel thomas.dan...@intel.com
The previous comment about the WAs still applies. I reproduce it here
for
On Mon, Jul 14, 2014 at 09:53:38AM +, Gupta, Sourab wrote:
On Sun, 2014-07-06 at 18:29 +0530, sourab gupta wrote:
On Fri, 2014-06-20 at 10:02 +, Gupta, Sourab wrote:
From: Sourab Gupta sourab.gu...@intel.com
This patch series introduces a new gem create ioctl for user
From: Tim Gore tim.g...@intel.com
gem_mmap_offset_exhaustion relies on purgeable memory
allocations getting swapped out, freeing up physical
memory for further allocations. On Android we have no
swap partition so this cannot happen and the test gets
killed by the low memory killer before mmap
On Fri, Jul 25, 2014 at 10:00:19AM +0100, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
gem_mmap_offset_exhaustion relies on purgeable memory
allocations getting swapped out, freeing up physical
memory for further allocations. On Android we have no
swap partition so this
-Original Message-
From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel
Vetter
Sent: Friday, July 25, 2014 10:07 AM
To: Gore, Tim
Cc: intel-gfx@lists.freedesktop.org; daniel.vet...@ffwll.ch
Subject: Re: [PATCH] intel-gpu-tools: skip gem_mmap_offset_exhaustion on
On Fri, Jul 25, 2014 at 10:30:09AM +0200, Daniel Vetter wrote:
On Thu, Jul 24, 2014 at 05:04:09PM +0100, Thomas Daniel wrote:
From: Oscar Mateo oscar.ma...@intel.com
In this patch:
commit 78382593e921c88371abd019aca8978db3248a8f
Author: Oscar Mateo oscar.ma...@intel.com
Date:
On Fri, Jul 25, 2014 at 11:06:38AM +0200, Daniel Vetter wrote:
On Fri, Jul 25, 2014 at 10:00:19AM +0100, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
gem_mmap_offset_exhaustion relies on purgeable memory
allocations getting swapped out, freeing up physical
memory for
On Thu, 2014-07-24 at 01:33 +0200, Ian Kumlien wrote:
Try four, now including CC lists for the intel driver...
Could you give a try to the 2 patches at:
https://patchwork.kernel.org/patch/4437061/
If these don't fix the issue, could you send a full dmesg log with the
drm.debug=14 kernel option
On Fri, Jul 25, 2014 at 10:17:26AM +0100, Chris Wilson wrote:
On Fri, Jul 25, 2014 at 11:06:38AM +0200, Daniel Vetter wrote:
On Fri, Jul 25, 2014 at 10:00:19AM +0100, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
gem_mmap_offset_exhaustion relies on purgeable memory
On Fri, Jul 25, 2014 at 09:14:51AM +, Gore, Tim wrote:
-Original Message-
From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel
Vetter
Sent: Friday, July 25, 2014 10:07 AM
To: Gore, Tim
Cc: intel-gfx@lists.freedesktop.org; daniel.vet...@ffwll.ch
On 7/25/2014 1:20 PM, Daniel Vetter wrote:
On Fri, Jul 25, 2014 at 09:47:06AM +0200, Daniel Vetter wrote:
On Thu, Jul 24, 2014 at 03:16:12PM +0100, rafael.barba...@intel.com wrote:
From: Rafael Barbalho rafael.barba...@intel.com
This particular nasty presented itself while trying to register
On 07/25/2014 10:37 AM, Daniel Vetter wrote:
On Fri, Jul 25, 2014 at 10:17:26AM +0100, Chris Wilson wrote:
On Fri, Jul 25, 2014 at 11:06:38AM +0200, Daniel Vetter wrote:
On Fri, Jul 25, 2014 at 10:00:19AM +0100, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
On fre, 2014-07-25 at 12:28 +0300, Imre Deak wrote:
On Thu, 2014-07-24 at 01:33 +0200, Ian Kumlien wrote:
Try four, now including CC lists for the intel driver...
Could you give a try to the 2 patches at:
https://patchwork.kernel.org/patch/4437061/
If these don't fix the issue, could you
On Thu, Jul 24, 2014 at 6:12 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
In my review of
commit 98f75de40e9d83c3a90d294b8fd25fa2874212a9
Author: Rob Clark robdcl...@gmail.com
Date: Fri May 30 11:37:03 2014 -0400
drm: add object property typ
I asked for a check to make sure that
The Piglit test runner for intel-gpu-tools creates a new process group
for the test processes, so attempting to set terminal attributes causes
the process to receive SIGTTOU and be stopped. Since the test is not run
interactively in this case, the issue can be avoided by not setting
terminal
On 24 July 2014 17:38, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
commit 743dc7997aa9f5210055896940d87c88983dcda6
breaks the build under Android because version.h
is not created. This happens because the android
make executes from the ANDROID_BUILD_TOP directory
rather
On Sat, 2014-06-28 at 02:04 +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
CHV has two display PHYs so there are also two cmnlane power wells. Add
the approriate code to power the wells up/down.
Like on VLV we do the cmnreset assert/deassert
On Sat, 2014-06-28 at 02:04 +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Both VLV and CHV handle the cmnreset stuff in the power well code now,
so intel_reset_dpio() is no longer needed.
Signed-off-by: Ville Syrjälä
Daniel,
Your commit 2225a28fd916 (drm/i915: Ditch UMS config option) is
included in today's linux-next (ie, next-20140725). It removes the
Kconfig symbol DRM_I915_UMS.
It didn't remove the two (negative) checks for CONFIG_DRM_I915_UMS.
These checks are superfluous as they now will always
At the heart of this change is that the seqno is a too low level of an
abstraction to handle the growing complexities of command tracking, both
with the introduction of multiple command queues with execbuffer and the
potential for reordering with a scheduler. On top of the seqno we have
the
At the heart of this change is that the seqno is a too low level of an
abstraction to handle the growing complexities of command tracking, both
with the introduction of multiple command queues with execbuffer and the
potential for reordering with a scheduler. On top of the seqno we have
the
On Sat, 2014-06-28 at 02:04 +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Not sure if it's still there since chv has per-pipe power wells.
At least with current Punit this doesn't work. Also the display
irq handling would need to be adjusted
On Sat, 2014-06-28 at 02:04 +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
CHV has a power well for each pipe. Add the code to deal with them.
The Punit in current hardware doesn't seem ready for this yet, so
leave it iffed out.
On Sat, 2014-06-28 at 02:04 +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Add the TX wells for ports B and C just like on VLV.
Again Punit doesn't seem ready (or the wells don't even exist anymore)
so leave it iffed out.
Signed-off-by:
On Sat, 2014-06-28 at 02:04 +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Add the TX wells for port D. The Punit subsystem numbers are a total
guess at this time. Also I'm not sure these even exist. Certainly the
Punit in current hardware
On 25 July 2014 12:33, Thomas Wood thomas.w...@intel.com wrote:
On 24 July 2014 17:38, tim.g...@intel.com wrote:
From: Tim Gore tim.g...@intel.com
commit 743dc7997aa9f5210055896940d87c88983dcda6
breaks the build under Android because version.h
is not created. This happens because the
Signed-off-by: Thomas Wood thomas.w...@intel.com
---
tests/testdisplay.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/testdisplay.c b/tests/testdisplay.c
index f60e66d..20b0615 100644
--- a/tests/testdisplay.c
+++ b/tests/testdisplay.c
@@ -670,7 +670,7 @@ static void
Yes, timer can be helpful. A revised proposal is that flip trigger +
timer to cover together. I'll come up with more details soon.
- Daisy
On 7/25/2014 12:22 AM, Daniel Vetter wrote:
On Thu, Jul 24, 2014 at 01:28:21PM -0700, Jesse Barnes wrote:
If that won't work, you could just use a
Most tests use a printable character as the value for getopt to return,
so avoid conflicts by using non-printing values for the standard options.
Signed-off-by: Thomas Wood thomas.w...@intel.com
---
lib/igt_core.c | 23 +++
1 file changed, 15 insertions(+), 8 deletions(-)
2014-07-25 13:08 GMT-03:00 Thomas Wood thomas.w...@intel.com:
Most tests use a printable character as the value for getopt to return,
so avoid conflicts by using non-printing values for the standard options.
Instead of this patch, isn't there any way to verify if the tests are
using any
On Thu, Jul 24, 2014 at 09:44:41AM +0800, Chen, Tiejun wrote:
On 2014/7/24 4:54, Konrad Rzeszutek Wilk wrote:
On Sat, Jul 19, 2014 at 12:27:21AM +, Kay, Allen M wrote:
For the MCH PCI registers that do need to be read - can you tell us which
ones those are?
In
Hi all,
New -testing cycle with cool stuff:
- Ditch UMS support (well just the config option for now)
- Prep work for future platforms (Sonika Jindal, Damien)
- runtime pm/soix fixes (Paulo, Jesse)
- psr tracking improvements, locking fixes, now enabled by default!
- rps fixes for chv (Deepak,
On Thu, May 22, 2014 at 07:00:50PM +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Share the waitqueue that drm_irq uses when performing the vblank evade
trick for atomic pipe updates.
v2: Keep intel_pipe_handle_vblank() (Chris)
On Fri, Jul 25, 2014 at 2:14 PM, Paul Bolle pebo...@tiscali.nl wrote:
Your commit 2225a28fd916 (drm/i915: Ditch UMS config option) is
included in today's linux-next (ie, next-20140725). It removes the
Kconfig symbol DRM_I915_UMS.
It didn't remove the two (negative) checks
we have reconsidered good suggestions and evaluated performance and complexity
again.
Timer Constant callback would continuously wake up CPU and entire
package, results in lower CPU and package C-state and shorter battery life,
especially for standby time.
execbuf is a good one, and we had
On Wed, Jul 16, 2014 at 04:05:59PM +0100, alistair.mcau...@intel.com wrote:
From: McAulay, Alistair alistair.mcau...@intel.com
This patch is to address Daniels concerns over different code during reset:
http://lists.freedesktop.org/archives/intel-gfx/2014-June/047758.html
The reason for
On Fri, Jul 25, 2014 at 10:06:27AM +0530, Sharma, Shashank wrote:
Thanks for your time, and review comments Matt.
I appreciate the suggestions by you, Daniel.
But I need a few more details, and I have a few concerns with the
design you suggest, please find my comments inline.
Regards
50 matches
Mail list logo
