Announcement

Collapse
No announcement yet.

RandR 1.2 Enters RadeonHD Master

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • RandR 1.2 Enters RadeonHD Master

    Phoronix: RandR 1.2 Enters RadeonHD Master

    Minutes after the release of the RadeonHD v0.0.3 driver, the initial-randr branch for x86-video-radeonhd was merged into master. What this means is that you no longer need to checkout this separate branch but that all of the RandR 1.2 support is now in the mainline code for this open-source driver.

    http://www.phoronix.com/vr.php?view=NjIxNw

  • #2
    well the only question left now is

    WTF

    is RandR 1.2 !!!!!!!

    GRRRRRRRR to articles that dont explain acronyms or assume terminology is known.

    Comment


    • #3
      Randr 1.2 is output extension that lets you to switch resolutions and dynamically plug output devices. I think it was covered a lot few months ago. And if you do not know acronyms it is much easier to search in google than in a forum.
      Last edited by Mithrandir; 11-22-2007, 06:10 AM.

      Comment


      • #4
        It stands for Resize AND Rotate (RANDR) extension. Everything seemed more clear once I understood that

        Comment


        • #5
          I just downloaded and installed the radeonhd 0.0.3-5.1 rpm on Fedora 8 with a Radeon 1650 Pro (RV535) card and two LCDs, and I am able to sue the RandR to set up a dual monitor config. Most excellent!

          Here's the output from xrandr -q:
          Screen 0: minimum 320 x 200, current 3360 x 1050, maximum 3360 x 1050
          DVI-I_CRT1_DFP1/DAC_A disconnected
          DVI-I_CRT1_DFP1/TMDS_A connected 1680x1050+0+0 473mm x 296mm
          1680x1050 60.0*+
          1280x1024 75.0 59.9
          1440x900 75.0 59.9
          1280x960 59.9
          1360x765 59.8
          1152x864 74.8
          1280x720 59.9
          1024x768 75.1 70.1 60.0
          832x624 74.6
          800x600 72.2 75.0 60.3 56.2
          640x480 75.0 72.8 66.7 60.0
          720x400 70.1
          SVIDEO_TV1/DAC_B disconnected
          DVI-I_CRT2_DFP3/DAC_B disconnected
          DVI-I_CRT2_DFP3/TMDS_B unknown connection 1680x1050+1680+0 473mm x 296mm
          1680x1050 60.0*+
          1280x1024 75.0 59.9
          1440x900 75.0 59.9
          1280x960 59.9
          1360x765 59.8
          1152x864 74.8
          1280x720 59.9
          1024x768 75.1 70.1 60.0
          832x624 74.6
          800x600 72.2 75.0 60.3 56.2
          640x480 75.0 72.8 66.7 60.0
          720x400 70.1
          And here's my xorg.conf for the dual monitor setup:
          # Xorg configuration

          Section "ServerLayout"
          Identifier "RandR Multihead layout"
          Screen 0 "Screen0" 0 0
          InputDevice "Keyboard0" "CoreKeyboard"
          EndSection

          Section "InputDevice"
          Identifier "Keyboard0"
          Driver "kbd"
          Option "XkbModel" "pc105"
          Option "XkbLayout" "us+inet"
          EndSection

          Section "Monitor"
          Identifier "DVI-I_CRT1_DFP1/TMDS_A"
          ModelName "Acer AL2216W"
          Option "PreferredMode" "1680x1050"
          Option "LeftOf" "DVI-I_CRT2_DFP3/TMDS_B"
          Option "DPMS" "on"
          EndSection

          Section "Monitor"
          Identifier "DVI-I_CRT2_DFP3/TMDS_B"
          ModelName "Acer AL2216W"
          Option "PreferredMode" "1680x1050"
          # Option "RightOf" "DVI-I_CRT1_DFP1/TMDS_A"
          Option "DPMS" "on"
          EndSection

          Section "Device"

          Identifier "Videocard0"
          Driver "radeonhd"
          BoardName "Radeon X1650 Pro"
          EndSection

          Section "Screen"
          Identifier "Screen0"
          Device "Videocard0"
          Monitor "DVI-I_CRT1_DFP1/TMDS_A"
          DefaultDepth 24
          SubSection "Display"
          Viewport 0 0
          Virtual 3360 1050
          Depth 24
          EndSubSection
          EndSection
          I have tried dual monitor configs with various drivers in the last couple days, and one oddity is that the various drivers behave slightly differently. My LCD/DVI monitor for isntance shows up as the following:
          radeonhd: DVI-I_CRT1_DFP1/TMDS_A
          radeon: DVI-1
          nv: DVI1

          The various drivers also recognize different subsets of the RandR-related commands in xorg.conf. Functionality and stability are most improtant, but i hope eventually the usage of the various drivers converges.

          Comment


          • #6
            Originally posted by CrystalCowboy View Post
            I have tried dual monitor configs with various drivers in the last couple days, and one oddity is that the various drivers behave slightly differently. My LCD/DVI monitor for isntance shows up as the following:

            radeonhd: DVI-I_CRT1_DFP1/TMDS_A
            radeon: DVI-1
            nv: DVI1
            I think this is just a case of the radeonhd driver giving out more information to help with troubleshooting.

            All three drivers are saying "you're on the DVI-I physical connector". The radeonhd driver is also saying :

            - the DVI-I connector is wired to the CRT1 and DFP1 chip outputs

            - the DFP1 chip output is being fed by the TMDSA block of the ASIC (the first of two digital output blocks, the other is LVTMA)

            The new display controller is a lot more flexible than the old one, so there are a lot more ways to wire a chip into a system, particularly a laptop with dock.
            Last edited by bridgman; 11-23-2007, 12:11 PM.

            Comment


            • #7
              Originally posted by bridgman View Post
              I think this is just a case of the radeonhd driver giving out more information to help with troubleshooting.
              Indeed. But egbert rewrote this to read "DVI-[IDA] 1/2" instead. This is a lot more straightforward.

              Comment


              • #8
                Translation: either DVI-I, DVI-D or DVI-A depending on the outputs attached. And then they are simply counted.

                So "DVI-I 1" and "DVI-I 2" will be the common cases.

                For RandR, this of course needs to get split out again.

                Comment

                Working...
                X