Announcement

Collapse
No announcement yet.

An Updated ATI Kernel Mode-Setting Driver

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

  • #31
    Originally posted by dkasak View Post
    so I'm not surprised. Disappointed. Not surprised. I've already had to disable AGP and AccelDFS to get rid of graphics corruption under EXA
    I stopped being being surprised or disappointed long ago. AGP just simply apparently doesn't work properly, will be getting rid of the last computer I have with that soon enough.

    Comment


    • #32
      *sigh*
      I sooo hope I'll see all that fancy stuff work on my R600 type cards/chips in 2.6.32. Sometimes I regret a little havin given away my R500 one.

      Comment


      • #33
        Originally posted by dkasak View Post
        Really? Yes well that's how I'd describe performance at this point I suppose, so I'm not surprised. Disappointed. Not surprised. I've already had to disable AGP and AccelDFS to get rid of graphics corruption under EXA ( and DRI1 ). It's hard to avoid the feeling that I'm going backwards.
        Good luck, the OSS driver from git was working great last time I used it on my laptop. It was also able to play a 720p movie on my 26" screen and I was able to play tremulous at the resolution of 1920*1200 with an average of 35 fps.

        Now, I'm using fglrx with my brand new HD4770. 3D performance is really great but user experience is not really good on kde4 and flash.

        Comment


        • #34
          What has changed in the KMS code since it was included in the kernel as a staging driver? With this patch + drm-next applied over a 2.6.29 kernel I could get a 1680x1050 console at startup with my HD3850, but with the staging driver in the .31-rcX kernel I simply get 80x25 and no errors in dmesg when I select CONFIG_DRM_RADEON_KMS.

          Is r6xx support going backwards? I know it's not supposed to work yet, but it seemed to be closer a month ago with the patch than right now :P

          Comment


          • #35
            R300 KMS is getting closer !

            For more info :
            http://www.phoronix.com/forums/showp...76&postcount=2

            Comment


            • #36
              Jerome's initial r6xx/r7xx KMS support patch is here:
              http://people.freedesktop.org/~gliss...x-chipse.patch

              Comment


              • #37
                That is one huge patch!

                So Red Hat gave R100-R500 KMS to David and R600-R700 to Jerome to work on?

                Comment


                • #38
                  While searching for the mailinglist post, Google showed a commercial for "KMS hair Care".

                  I had to click on that one!

                  Comment


                  • #39
                    Originally posted by agd5f View Post
                    Jerome's initial r6xx/r7xx KMS support patch is here:
                    http://people.freedesktop.org/~gliss...x-chipse.patch
                    Mmmm... it doesn't apply cleanly over 2.6.31-rc5 or rc4.

                    Comment


                    • #40
                      Originally posted by Fran View Post
                      Mmmm... it doesn't apply cleanly over 2.6.31-rc5 or rc4.
                      If my memory is right, they are working on a 2.6.28 kernel, and, when they are ready, they port it to the latest kernel. 2.6.28 is the version most users are running

                      Comment


                      • #41
                        Hmm, I've just installed all the KMS bits for R200 and it doesn't seem to be working.

                        I get a framebuffer console that works fine...
                        Code:
                        ~ $ dmesg | grep modesetting
                        [    2.199528] [drm] radeon default to kernel modesetting.
                        [    2.199606] [drm] radeon kernel modesetting enabled.
                        But when I go to start X I get the old monitor on-off-on flicker and this:
                        Code:
                        ~ $ grep -i KMS /var/log/Xorg.0.log
                        (II) [KMS] drm report modesetting isn't supported.
                        And just to rub it in I seem to have no HW accel at all, I'm getting 1-second lags just moving the mouse over buttons.

                        (btw this is about the 5th time in a row I've had my xmodmap settings broken by an X11 upgrade, what gives?)

                        Comment


                        • #42
                          Originally posted by Ant P. View Post
                          (btw this is about the 5th time in a row I've had my xmodmap settings broken by an X11 upgrade, what gives?)
                          Maybe this can help?

                          http://forums.fedoraforum.org/showthread.php?t=224444

                          Comment


                          • #43
                            Originally posted by Louise View Post
                            Thanks for that, I didn't think of using "clear Lock" there, will try that. (edit: nope, still screwy...)

                            This was all I had in my .xmodmap file:
                            Code:
                            remove Lock = Caps_Lock
                            keysym Caps_Lock = Escape
                            I seem to have terrible luck with keyboard things in X... this time it broke all my modifier keys, last time the keyboard stopped responding if I had xmodmap in my xinitrc, and the first time I used evdev years ago the keys were pretty much randomised...

                            Comment


                            • #44
                              Originally posted by MPF View Post
                              If my memory is right, they are working on a 2.6.28 kernel, and, when they are ready, they port it to the latest kernel. 2.6.28 is the version most users are running
                              That's what was happening for the 6xx/7xx 3d drm support, but I think glisse was using a more recent kernel for his work, probably an earlier 2.6.31 since that's where KMS first merged upstream.

                              Comment


                              • #45
                                Originally posted by agd5f View Post
                                Jerome's initial r6xx/r7xx KMS support patch is here:
                                http://people.freedesktop.org/~gliss...x-chipse.patch
                                That says it provides no hardware acceleration. Aside from testing purposes or curiosity, why would someone else want to use this patch? Without EXA and XV things would be pretty unbearable... The 1680x1050 screen on my laptop means a lot of pixels to shove around using just the CPU.

                                (Just trying to talk myself into/out of applying the patch to my 2.6.31-rc5 tree......)

                                Comment

                                Working...
                                X