[Intel-gfx] testing for quarterly release (2008-07)
The Fungi
fungi at yuggoth.org
Sun Aug 3 07:20:48 CEST 2008
On Tue, Jul 01, 2008 at 04:37:23PM +0800, Jin, Gordon wrote:
> I believe your testing would contribute to the quality for the final
> release. Below testing will be especially appreciated:
[...]
> -- HDMI
>
> xf86-video-intel 2.4 provides HDMI support for both integrated HDMI and
> SDVO HDMI. So for people using Asus P5E-VM G35 board (with SDVO HDMI),
> please give it a try.
[...]
So far so good (I would have tried earlier but turns out a PCI-E
riser in my system was silently disabling/overriding my HDMI
interface). I'm only effectively able to test 640x480 to my HDTV
because I suspect the driver needs an EDID quirk for it. With an ATI
Radeon and a DVI->HDMI cable I was successfully using:
Section "Device"
Identifier "ATI Radeon 9000/RV250"
Driver "ati"
Option "IgnoreEDID" "on"
EndSection
Section "Monitor"
Identifier "Sony KDF-60XS955 HDTV"
HorizSync 15-46
VertRefresh 59-61
DisplaySize 320 180
Mode "1280x720"
DotClock 74.25
HTimings 1280 1320 1376 1650
VTimings 720 722 728 750
EndMode
Option "PreferredMode" "1280x720"
EndSection
Key here is that I have to override EDID checking because this HDTV
only claims support for 480p and 1080i for some reason, but its
native resolution is actually 720p. Trying IgnoreEDID (or NoEDID for
the DDC module) with the intel driver didn't keep it from believing
EDID according to the log, and I see in the list archives that
adding a quirk in the driver is the preferred solution anyway.
Should I file a bug report requesting this? Granted, the timings I
used are probably not optimal as I had to recenter the image through
my television's service menus. Here's what my EDID looks like:
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0x11110 "Intel(r)Q965/Q963/G965 Graphics Chip Accelerated VGA BIOS"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
EDID claims 1 more blocks left
*********** Something special has happened!
Please contact the author, John Fremlin
E-mail: one of vii at altern.org,vii at mailcc.com,vii at mailandnews.com
Please include full output from this program (especially that to stderr)
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
EDID claims 1 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:fc
Identifier "SONY TV"
VendorName "SNY"
ModelName "SONY TV"
# Block type: 2:0 3:fc
# Block type: 2:0 3:fd
HorizSync 15-46
VertRefresh 59-61
# Max dot clock (video bandwidth) 80 MHz
# DPMS capabilities: Active off:no Suspend:no Standby:no
Mode "1920x540" # vfreq 60.053Hz, hfreq 33.750kHz
DotClock 74.250000
HTimings 1920 2008 2052 2200
VTimings 540 542 547 562
Flags "Interlace" "+HSync" "+VSync"
EndMode
Mode "720x480" # vfreq 59.940Hz, hfreq 31.469kHz
DotClock 27.000000
HTimings 720 736 798 858
VTimings 480 489 495 525
Flags "-HSync" "-VSync"
EndMode
# Block type: 2:0 3:fc
# Block type: 2:0 3:fd
EndSection
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP(fungi at yuggoth.org); IRC(fungi at irc.yuggoth.org#ccl); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER(fungi at yuggoth.org);
MUD(fungi at katarsis.mudpy.org:6669); WWW(http://fungi.yuggoth.org/); }
More information about the Intel-gfx
mailing list