Announcement

Collapse
No announcement yet.

Open source "Radeon" driver: vsync, vblank_mode, tearing and (open)GL

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

  • #16
    I believe underscan was recently enabled by default with HDMI outputs and HD timings. There is an xrandr option to turn it off, will see if I can find it...

    Comment


    • #17
      Here we go :

      http://www.phoronix.com/forums/showp...12&postcount=3

      xrandr --output DVI-0 --set underscan off

      (adjust for whatever your output is called)

      Comment


      • #18
        Thank you for your reply. But when I use xrandr to see if "underscan" is a property which I can set with "--set" it is not. See output of xrandr --prop w/ KMS enabled:
        Code:
        $ xrandr --prop
        
        Screen 0: minimum 320 x 200, current 1280 x 960, maximum 4096 x 4096
        VGA-0 connected 1280x960+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
        	load detection: 1 (0x00000001)	range:  (0,1)
           1280x960       60.0*+
           1680x1050      60.0  
           1600x1024      60.2  
           1400x1050      60.0  
           1280x1024      60.0  
           1440x900       59.9  
           1360x768       59.8  
           1152x864       75.0     75.0     70.0     60.0  
           1024x768       85.0     75.0     70.1     60.0  
           832x624        74.6  
           800x600        85.1     72.2     75.0     60.3     56.2  
           848x480        60.0  
           640x480        85.0     72.8     75.0     59.9     59.9  
           720x400        85.0  
           640x400        85.1  
           640x350        85.1  
        DVI-0 disconnected (normal left inverted right x axis y axis)
        	load detection: 1 (0x00000001)	range:  (0,1)
        S-video connected (normal left inverted right x axis y axis)
        	tv standard:	pal
        		supported: ntsc         pal          pal-m        pal-60      
        		           ntsc-j       scart-pal    pal-cn       secam       
        	load detection: 1 (0x00000001)	range:  (0,1)
           800x600        59.9 +
           640x480        59.9
        And the output for the S-video part of xrandr --prop w/ KMS DISabled:
        Code:
        S-video disconnected (normal left inverted right x axis y axis)
        	tv_standard: pal
        	tv_vertical_position: 0 (0x00000000)	range:  (-5,5)
        	tv_horizontal_position: 0 (0x00000000)	range:  (-5,5)
        	tv_horizontal_size: 0 (0x00000000)	range:  (-5,5)
        	load_detection: 0 (0x00000000)	range:  (0,1)
        Notice that magically some very useful settings appear with which I can set overscan myself. With kms enabled, I seem not to be able to do that. Why?

        Since there is no property called "underscan" its no surprise that if I try to set it I get an error:
        Code:
        $ xrandr --output S-video --set underscan off
        
        X Error of failed request:  BadName (named color or font does not exist)
          Major opcode of failed request:  149 (RANDR)
          Minor opcode of failed request:  11 (RRQueryOutputProperty)
          Serial number of failed request:  29
          Current serial number in output stream:  29

        Comment


        • #19
          Wonder if 2.6.35 is recent enough... Seems like the guy got overscan in the other thread from 2.6.35-git2 to 2.6.35-git3. (and no, I don't personally recommend using those; rather use git with 2.6.35 release and then pull from airlied's drm-next or whatever branch on top of it; airlied free to strangle me if I gave the wrong branch )

          Comment


          • #20
            Originally posted by nanonyme View Post
            Wonder if 2.6.35 is recent enough... Seems like the guy got overscan in the other thread from 2.6.35-git2 to 2.6.35-git3. (and no, I don't personally recommend using those; rather use git with 2.6.35 release and then pull from airlied's drm-next or whatever branch on top of it; airlied free to strangle me if I gave the wrong branch )
            I am fairly sure 2.6.35 is too old. You must get your hands on the fancy new 2.6.35-git3+ technology to xrandr --output DVI-0 --set underscan off with KMS with r600. Underscan is now enabled by default for this driver and I find this very sad and depressing and I kind of wish those behind this conspiracy would be shot in their heads and barried in shallow graves. Mr. Jansen (Danish person indicated?) is using r300, not r600, but I am fairly sure the KMS underscan changes where forced upon users of both chips at the same time.

            It's hard to say what kernel mr Jansen should go ahead and use, I haven't tried the fancy new 2.6.35-git16 yet but a quick glance at http://www.kernel.org/diff/diffview....6.35-git16.bz2 does not indicate that it will not make computers explode.

            Anyway, good luck!!1!

            Comment


            • #21
              Note that if you do what I said instead of using git snapshots, you get a stable kernel on every other component except DRM. That makes imo quite a bit more sense than using using just-pulled-into-Linus'-tree for everything.

              Comment


              • #22
                1. I use an R300 Ati card. I was under the impression that that one's driver (= radeon) is quite different from the R600 one (= radeonhd). But maybe your tips do work on mine.

                2. Am I right that (at the time of writing) no Linux distribution what so ever on the whole wide world comes with a 2.6.35+ kernel? And that I must compile one myself from source? Not that I'd mind but I'm surprised nobody else is having tis prob...

                3. I do not use DVI for TV out, I use the S-video (= SVHS) out. I don't think that makes a lot of difference , but I thought I'd mention it.

                Anyway, do you think that the extra options that I lost after switching to KMS mode will appear again after booting w/ a supernew kernel?

                Comment


                • #23
                  Originally posted by Meneer Jansen View Post
                  1. I use an R300 Ati card. I was under the impression that that one's driver (= radeon) is quite different from the R600 one (= radeonhd). But maybe your tips do work on mine.
                  All cards should now use radeon driver and KMS.
                  Originally posted by Meneer Jansen View Post
                  2. Am I right that (at the time of writing) no Linux distribution what so ever on the whole wide world comes with a 2.6.35+ kernel? And that I must compile one myself from source? Not that I'd mind but I'm surprised nobody else is having tis prob...
                  Very likely true. You might find some special repositories that make newer modules/kernels so you don't have to compile yourself, who knows.
                  Originally posted by Meneer Jansen View Post
                  Anyway, do you think that the extra options that I lost after switching to KMS mode will appear again after booting w/ a supernew kernel?
                  It might, don't know before you try. The thing is that KMS moved modesetting completely away from radeon/radeonhd drivers into kernel and some features that were in the old userspace modesetting might have been or might still be missing from kernel modesetting. Reporting bugs on missing functionality is a good habit.

                  Comment


                  • #24
                    ps. There is and never has been a separate kernel module for radeonhd, the two different drivers were just as X userspace display drivers.

                    Comment


                    • #25
                      Originally posted by Meneer Jansen View Post
                      Nope. Seems there are some more quirks to this. Now I can't overscan anymore. The picture does not cover the whole TV screen anymore. That is: without KMS the output of the command "xrandr --prop" is:
                      Code:
                      S-video disconnected (normal left inverted right x axis y axis)
                      	tv_standard: pal
                      	tv_vertical_position: 0 (0x00000000)	range:  (-5,5)
                      	tv_horizontal_position: 0 (0x00000000)	range:  (-5,5)
                      	tv_horizontal_size: 0 (0x00000000)	range:  (-5,5)
                      	load_detection: 0 (0x00000000)	range:  (0,1)
                      Meaning that I can overscan (i.e. set hor/vert position and the hor. size). However if I boot with KMS then these parameters do not appear when I ask for the TV's properties w/ "xrandr --prop". And only with KMS the GL output (vsync) does noet tear or stutter. AAaaaaaaaaaaaaaaaaaaarrrrrrrrrrrggggghhhhhhhhhhh.

                      How can I fix this and what's the matter w/ xrandr if KMS is activated?
                      Those options were never ported to kms. It should be pretty easy to add them.

                      Comment


                      • #26
                        Originally posted by agd5f View Post
                        Those options were never ported to kms. It should be pretty easy to add them.
                        Jippee. Since you are the driver developer: when do you think that will be included/ported? And will I have to update my kernel, the redeon driver or dri, mesa etc.?

                        (The Ubuntu 2.6.35.1 precompiled kernel was released today and I upgraded to that one. But, no success yet of course.)

                        Comment


                        • #27
                          Originally posted by Meneer Jansen View Post
                          Jippee. Since you are the driver developer: when do you think that will be included/ported? And will I have to update my kernel, the redeon driver or dri, mesa etc.?
                          You will only have to update your kernel. I'm not sure when I will get to it. I'm happy to review a patch if someone else beats me to it.

                          Comment


                          • #28
                            Could anybody here tell me what is the currently suggested choice for video output in mplayer for an ati 4850(that is r700)? gl2, xv or what?

                            Comment


                            • #29
                              Originally posted by MisterIO View Post
                              Could anybody here tell me what is the currently suggested choice for video output in mplayer for an ati 4850(that is r700)? gl2, xv or what?
                              Linux? Then xv is always the prefered method.

                              Comment


                              • #30
                                Originally posted by agd5f View Post
                                You will only have to update your kernel. I'm not sure when I will get to it. I'm happy to review a patch if someone else beats me to it.
                                I sincerely hope that you will add said xrandr functionality to the kernel. If you write a patch, can I add that to any kernel source w/ the old command "patch -p0 < patch-file-name-here"? If so, then I'll try to compile a kernel myself if you write a patch. I am really very eagerly waiting for an updated kernel...

                                P.S. Some of those 2.6.35 kernels make my PC "hang" a couple of minuted after booting. Known bug? Don't have those probs w/ the 2.6.32 Ubuntu Lucid kernel.

                                Comment

                                Working...
                                X