Bug 2367 - no external DVI output on radeon dualhead configuration
Summary: no external DVI output on radeon dualhead configuration
Status: RESOLVED DUPLICATE of bug 2273
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: Other Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-24 03:34 UTC by Soeren Sonnenburg
Modified: 2005-06-01 10:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Soeren Sonnenburg 2005-01-24 03:34:40 UTC 
It is not possible to configure xorg to use the _EXTERNAL_ DVI port on a radeon
M9 card.

The machine here is a tibook 15" (ppc machine) and internal display only,
internal display + external vga output, work nicely in merged framebuffer mode
(mirror or separate screens) as well as dualhead (or xinerema) setup.

However DVI only works for the external display when the internal display is in
mirror mode (and one needs to specify panel sizes for both devices). It also
only works if tmds is specified FIRST in the MonitorLayout list (swapping to:
lvfs, tmds makes X just crash). However it works for mergedfb and seperately
specified screens and X claims to have generated a large mergedfb but still the
internal display just mirrors the upper left part of the external DFP (as the
internal DFP's resolution is smaller).

The relevant part from the configs:

Section "Device"
        Identifier      "ATI Radeon Internal"
        Driver          "radeon"
        BusID           "PCI:0:16:0"
        Option "MonitorLayout" "TMDS,LVDS"
        Option "PanelSize" "1280x1024"
        Option "MergedFB" "On"
        Option "CRT2HSync" "30-100"
        Option "CRT2VRefresh" "50-150"
        Option "CRT2Position" "RightOf"
        Option "MetaModes" "1280x1024-1280x854"
        Option "DynamicClocks" "true"
        VendorName  "ATI Technologies Inc"
        BoardName   "Radeon Mobility M7 LW [Radeon Mobility 7500]"
EndSection
Comment 1 Alex Deucher 2005-01-28 14:37:21 UTC 
There are currently hardcoded crtc to output mappings in the radeon driver so
ATM crtc2 can't drive internal TMDS.  I plan to fix this as soon as I have time.

*** This bug has been marked as a duplicate of 2273 ***

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.