On Thu, Jan 30, 2014 at 09:53:54AM -0500, Alan Stern wrote:
On Tue, 28 Jan 2014, Daniel Vetter wrote:
I think I need a bit more debug output first. Can you please apply the
below patch to drm-intel-nightly and then grab a drm.debug=0xe dmesg from
boot?
The dmesg output is below. Since
On Thu, 30 Jan 2014, Daniel Vetter wrote:
Ok, I seem to have been truly blind all the time. This seems to have been
fallout from
commit b6c5164d7bf624f3e1b750787ddb983150c5117c
Author: Daniel Vetter daniel.vet...@ffwll.ch
Date: Fri Apr 12 18:48:43 2013 +0200
drm/i915: Fixup Oops
On Wed, Jan 8, 2014 at 7:43 PM, Ville Syrjälä
ville.syrj...@linux.intel.com wrote:
The log looks fairly clear to me:
1. initially panel fitter is enabled on pipe B, and pipe B is outputting
to LVDS and VGA. Border is enabled.
2. pipe A gets enabled outputting to LVDS. This will overwrite
On Tue, Jan 28, 2014 at 06:17:00PM +0100, Daniel Vetter wrote:
On Wed, Jan 8, 2014 at 7:43 PM, Ville Syrjälä
ville.syrj...@linux.intel.com wrote:
The log looks fairly clear to me:
1. initially panel fitter is enabled on pipe B, and pipe B is outputting
to LVDS and VGA. Border is
On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern st...@rowland.harvard.edu wrote:
Don't bother. I'll redo it using the drm-intel-nightly branch, but I
won't have time for a few days.
My apologies for the delay in getting around to this. Can you please
test the patch i've just posted?
On Mon, Jan 27, 2014 at 10:30:11AM -0500, Alan Stern wrote:
On Mon, 27 Jan 2014, Daniel Vetter wrote:
On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern st...@rowland.harvard.edu
wrote:
Don't bother. I'll redo it using the drm-intel-nightly branch, but I
won't have time for a few days.
On Mon, 27 Jan 2014, Daniel Vetter wrote:
By the way, I tried getting an up-to-date version of your
drm-intel-nightly branch, and ended up with the following:
$ git clone --depth 1 -b drm-intel-nightly
http://cgit.freedesktop.org/~danvet/drm-intel/
Cloning into 'drm-intel'...
On Mon, 27 Jan 2014, Daniel Vetter wrote:
On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern st...@rowland.harvard.edu wrote:
Don't bother. I'll redo it using the drm-intel-nightly branch, but I
won't have time for a few days.
My apologies for the delay in getting around to this. Can you please
On Mon, Jan 27, 2014 at 11:05:47AM -0500, Alan Stern wrote:
On Mon, 27 Jan 2014, Daniel Vetter wrote:
By the way, I tried getting an up-to-date version of your
drm-intel-nightly branch, and ended up with the following:
$ git clone --depth 1 -b drm-intel-nightly
On Mon, 27 Jan 2014, Daniel Vetter wrote:
On Mon, Jan 27, 2014 at 11:05:47AM -0500, Alan Stern wrote:
On Mon, 27 Jan 2014, Daniel Vetter wrote:
By the way, I tried getting an up-to-date version of your
drm-intel-nightly branch, and ended up with the following:
$ git clone
On Mon, Jan 13, 2014 at 03:16:42PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
On Tue, 7 Jan
On Mon, 13 Jan 2014, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
On Tue, 7 Jan
On Tue, 14 Jan 2014, Daniel Vetter wrote:
On Mon, Jan 13, 2014 at 03:16:42PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
On Tue, 7 Jan 2014, Daniel Vetter wrote:
I really want users to report
Hello,
The check_crtc_state() routine in drivers/gpu/drm/i915/intel_display.c
contains a whole bunch of WARN() statements (and so do other routines
in this source file, but this is the one I'm presently concerned
about). Is it really necessary for these to be WARN?
I don't see how it does any
On Wed, Jan 08, 2014 at 05:17:13PM +0100, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
On Tue, 7 Jan 2014, Daniel Vetter wrote:
I really want users to report these issues, and excessive WARNs seems
to be the only way to get those reports. Please boot
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
On Wed, 8 Jan 2014, Daniel Vetter wrote:
On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
On Tue, 7 Jan 2014, Daniel Vetter wrote:
I really want users to report these issues, and excessive WARNs seems
to be
On Tue, Jan 7, 2014 at 7:50 PM, Alan Stern st...@rowland.harvard.edu wrote:
After all, it's not like there's anything I can do to fix the hardware,
is there? And it doesn't look like the pipe state mismatch is going to
go away by itself. Or is this a genuine, fixable, software bug?
These are
18 matches
Mail list logo
