Bug 11894

Summary:

the second CRTC failed to put out video when using randr1.2 to change mode

Product:

xorg

Reporter:

LisaWu <liswu>

Component:

Driver/Radeon

Assignee:

xf86-video-ati maintainers <xorg-driver-ati>

Status:

RESOLVED FIXED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

git

Hardware:

All

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
add RADEON_CRTC2_CRT2_ON status check when define crtc2_gen_cntl register	none

Description LisaWu 2007-08-07 20:20:59 UTC

I've been testing the radeon driver for randr-1.2 lately on my FireGL V7100, I got the code from git xf86-video-ati randr-1.2 branch.
the card has two DVI port,I connected two CRTs to the card with DVI-VGA dongle and change output mode by issuing: xrandr --output DVI-1 --mode 1024x768(or other mode name).the wired thing happens that output DVI-0 fail to show video then. I have to use xrandr --output DVI-0 --mode 1024x768(or other mode name) to unblank it.

I believe this issue is caused by function RADEONInitCRTC2Registers.when issue randr to change DVI-1 mode, RADEONInitCRTC2Registers will be callded to define the CRTC2 registers for requested video mode, RADEON_CRTC2_CRT2_ON bit of register RADEON_CRTC2_GEN_CNTL was cleared in this function. 
To solve the problem, I suggest checking RADEON_CRTC2_CRT2_ON bit and keeping the status as it is.

Some extra information about this card: DVI-0 connected to TV-DAC, and DVI-1 connected to PRIMARY-DAC, thus RADEON_CRTC2_GEN_CNTL/RADOEN_CRTC2_CRT2_ON bit is responsible to enable CRT conneted to DVI-0.

Comment 1 LisaWu 2007-08-07 20:35:23 UTC

Created attachment 11042 [details] [review]
add RADEON_CRTC2_CRT2_ON status check when define crtc2_gen_cntl register

Comment 2 Alex Deucher 2007-08-07 21:09:54 UTC

Thanks!  fixed in git.
5c3f49e651c36f3bd14fa29359e24825d8f7f77f

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.