i810+modesetting: (EE) I810(0): phase 0 out of range

[Eric Anholt]

On Sat, 2006-11-11 at 12:12 +0100, Sixer wrote:
> On Nov 10, 2006, at 20:10 , Eric Anholt wrote:
> > OK, those bytes are filled in now, and should have an effect on the  
> > mode
> > you're choosing for your TV (guessing, since I don't have the log).
> 
> Do you mean you actually updated the source code?
> 
> If so, I did a git-clone and a checkout of the modesetting again, and  
> installed it. No difference however. Full logs are attached.

Hmm, interesting.  I think this is the first test of an interlaced mode
with our SDVO code.  Also, we're never setting the interlaced bit of the
DTD flags.  Perhaps try the attached patch?

If this doesn't work, we may need to see what the preferred timing looks
like for this mode.

> > On Fri, 2006-11-10 at 10:33 -0800, Eric Anholt wrote:
> >> On Fri, 2006-11-10 at 13:23 +0100, Sixer wrote:
> >>> Hi,
> >>>
> >>> I've got an Intel Mac Mini running Ubuntu Edgy with an i945GM  
> >>> chipset
> >>> hooked up to an HDTV with a 1920x540 native panel. The TV is hooked
> >>> up through DVI --> HDMI, which has been successfully tested under OS
> >>> X on the same machine and screen.
> >>>
> >>> With the i810 driver in conjunction with i915resolution, I wouldn't
> >>> get any valid mode retrieval from the display, i.e. all the modes
> >>> would come out 0x0 Hz 0KHz and Xorg (7.1.1) would not start.
> >>>
> >>> Now that I've installed the xf86-video-intel:modesetting driver by
> >>> Eric Anholt, at least Xorg starts successfully, but I don't get
> >>> anything on screen:
> >>>
> >>> (II) I810(0): Supported additional Video Mode:
> >>> (II) I810(0): clock: 74.2 MHz   Image Size:  576 x 324 mm
> >>> (II) I810(0): h_active: 1920  h_sync: 2448  h_sync_end 2492
> >>> h_blank_end 2640 h_border: 0
> >>> (II) I810(0): v_active: 540  v_sync: 542  v_sync_end 547 v_blanking:
> >>> 562 v_border: 0
> >>> (II) I810(0): Supported additional Video Mode:
> >>> (II) I810(0): clock: 74.2 MHz   Image Size:  576 x 324 mm
> >>> (II) I810(0): h_active: 1920  h_sync: 2008  h_sync_end 2052
> >>> h_blank_end 2200 h_border: 0
> >>> (II) I810(0): v_active: 540  v_sync: 542  v_sync_end 547 v_blanking:
> >>> 562 v_border: 0
> >>> (II) I810(0): Monitor name: LT-26S60
> >>> (II) I810(0): Ranges: V min: 59  V max: 61 Hz, H min: 15  H max: 46
> >>> kHz, PixClock max 80 MHz
> >>> (II) I810(0): Number of EDID sections to follow: 1
> >>> (II) I810(0): Valid Mode from Detailed timing table: 1920x540 (ht
> >>> 2640 hss 2448 hse 2492 vt 562 vss 542 vse 547)
> >>> (II) I810(0): Valid Mode from Detailed timing table: 1920x540 (ht
> >>> 2200 hss 2008 hse 2052 vt 562 vss 542 vse 547)
> >>> (II) I810(0): Total of 2 DDC mode(s) found.
> >>> [...]
> >>> (EE) I810(0): I830 Vblank Pipe Setup Failed
> >>> (EE) I810(0): Unable to read from SDVOCTRL_E for SDVOC slave 114.
> >>> (EE) I810(0): phase 0 out of range
> >>> (EE) I810(0): phase 0 out of range
> >>>
> >>> My xorg.conf has the exact vertical and horizontal refresh rates for
> >>> my TV.
> >>>
> >>> I actually prefer to use 1280x720. If I take out the "1920x540"
> >>> resolution from my Modes and leave in 1280x720 however, Xorg will  
> >>> say
> >>> "No modes left for display" and dies. I was able to use 1280x720
> >>> under OS X.
> >>>
> >>> How do I at least get past the "phase 0 out of range" error, and if
> >>> possible, how do I get Xorg to accept a different videomode than the
> >>> native panel resolution?
> >>
> >> For the future, please attach full logs instead of cut-down ones.
> >>
> >> The phase 0 error message is debugging output recently added by  
> >> keithp,
> >> but I'm pretty sure it's bogus, or at least not relevant for what  
> >> you're
> >> dealing with.
> >>
> >> We ignore vertical and horizontal limits currently, as we're in the
> >> process of moving the configuration logic out of the driver and into
> >> RandR.  However, since you've got DDC over this output, the hope  
> >> would
> >> be that it would be choosing the correct mode.  So I don't know  
> >> what the
> >> issue would be that you're seeing.  Maybe just a problem in our SDVO
> >> mode setting bits -- we're leaving a couple of bytes zero, which is
> >> likely wrong.
> 
-- 
Eric Anholt                             anholt at FreeBSD.org
eric at anholt.net                         eric.anholt at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xf86-video-intel-sdvo-interlaced.diff
Type: text/x-patch
Size: 855 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20061113/1245d1ca/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20061113/1245d1ca/attachment.pgp>