[Bug 66516] [845g regression] No output on LVDS

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 5 09:27:17 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=66516

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|intel-gfx-bugs at lists.freede |daniel at ffwll.ch
                   |sktop.org                   |

--- Comment #6 from Chris Wilson <chris at chris-wilson.co.uk> ---
66e3d5c09940d08d94b03e65b420fadaa7484318 is the first bad commit
commit 66e3d5c09940d08d94b03e65b420fadaa7484318
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date:   Sun Jun 16 21:24:16 2013 +0200

    drm/i915: move i9xx dpll enabling into crtc enable function

    Now that we have the proper pipe config to track this, we don't need
    to write any registers any more.

    Note that for platforms without DPLL_MD (pre-gen4) which store the
    pixel mutliplier in the DPLL register I've decided to keep the
    seemingly "redundant" write: The comment right below saying "do this
    trice for luck" doesn't instill confidence ...

    v2: Drop a few now unnecessary local variables and switch the enable
    function to take a struct intel_crtc * to simply arguments.

    v3: Rebase on top of the newly-colored BUG_ON.

    v4: Amend commit message to alliviate Imre's comment about the
    redudant DPLL write for the pixel mutliplier.

    Cc: Imre Deak <imre.deak at intel.com>
    Cc: Jani Nikula <jani.nikula at linux.intel.com>
    Reviewed-by: Imre Deak <imre.deak at intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

Definitely this time.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130705/f7d29a43/attachment.html>


More information about the intel-gfx-bugs mailing list