Announcement

Collapse
No announcement yet.

Open ATI Driver To Receive PowerPlay Push?

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

  • #41
    Originally posted by Neuro View Post
    Why? Were they late? Or are they doing something hackish? Any chance of them getting into the mainline kernel in the next version (2.6.34 perhaps)?
    Some users get flashes on the screen when the clocks change. At this point 2.6.33 is closed for new features. Hopefully something will land in 2.6.34.

    Comment


    • #42
      Originally posted by signor_rossi View Post
      Ups, knew about the security fixes but forgot that you don't get new package versions, but I am also used completely to the rolling release scheme now after almost ten years with Gentoo and Arch. :-)
      Then you want to switch to testing or unstable, which are both rolling releases. Unstable is debian's version of bleeding edge, it's still horridly out of date compared to say Gentoo, but that is where stuff goes first for Debian. After 10 days if a package passes certain tests (like not having any new bugs) the package gets copied to testing, so things are a bit safer there and only a little more outdated.

      I run Squeeze on my laptop, which is the current testing. Though I've got a self-built radeon stack from git code in there too. If you want a usable desktop rather than one that is years out of date I'd suggest switching to Squeeze.

      Comment


      • #43
        Originally posted by agd5f View Post
        Some users get flashes on the screen when the clocks change. At this point 2.6.33 is closed for new features. Hopefully something will land in 2.6.34.
        Would the patches apply to the DRM module or the KMS driver? If it's the KMS driver, I thought you could add all the features you want in staging.

        Comment


        • #44
          Originally posted by Ghworg View Post
          Then you want to switch to testing or unstable, which are both rolling releases. Unstable is debian's version of bleeding edge, it's still horridly out of date compared to say Gentoo, but that is where stuff goes first for Debian. After 10 days if a package passes certain tests (like not having any new bugs) the package gets copied to testing, so things are a bit safer there and only a little more outdated.

          I run Squeeze on my laptop, which is the current testing. Though I've got a self-built radeon stack from git code in there too. If you want a usable desktop rather than one that is years out of date I'd suggest switching to Squeeze.
          Squeeze's fglrx version is already too new for my X1600 card. I'm perfectly happy with Lenny, I don't need the newest stuff and if I needed, I can always compile them (I know, I'd have to compile all the dependencies too...)

          When I have more free time AND a faster internet, I may think about the "bleeding edge" again, but I'm sure I'm not alone settling with an "outdated" but stable system. I still like to read about the new stuff, though.

          Comment


          • #45
            Originally posted by pvtcupcakes View Post
            Would the patches apply to the DRM module or the KMS driver? If it's the KMS driver, I thought you could add all the features you want in staging.
            I always thought the DRM modules consisted of a generic drm module plus a specific radeon module (or nouveau-something, or intel-whatever, ...).

            I've never seen a KMS driver, but a radeon drm module with KMS enabled.

            But that's just me.

            Comment


            • #46
              Originally posted by Loris View Post
              I always thought the DRM modules consisted of a generic drm module plus a specific radeon module (or nouveau-something, or intel-whatever, ...).

              I've never seen a KMS driver, but a radeon drm module with KMS enabled.

              But that's just me.
              I mean the KMS option that's in the staging drivers. If these patches affect that code, I don't see any reason why Linus would try to stop those from being merged. That's the whole point of staging.

              If it gets in now, it can be tested by a lot more people, so when .34 rolls around KMS could be ready to get out of staging.

              But the radeon DRM module isn't in staging, so if it affects that, then I can see why it wouldn't be merged now.

              Comment


              • #47
                Originally posted by agd5f View Post
                The UMS drivers have basic support for lowering the engine clock and PCIE lanes either statically, or dynamically during DPMS on/off. The current KMS patches are here:
                http://people.freedesktop.org/~agd5f/pm/
                All radeons should be supported.
                these patches didn't apply to 2.6.33-rc2 and -rc3: is there a version which would work?

                Comment


                • #48
                  Originally posted by obino View Post
                  these patches didn't apply to 2.6.33-rc2 and -rc3: is there a version which would work?
                  Don't apply

                  0001-drm-radeon-kms-add-definitions-for-v4-power-tables.patch

                  in 2.6.33, as I think this one already got in.

                  The other patches should apply correctly.

                  Comment


                  • #49
                    Thank you: indeed they all applied and now my laptop is usable with KMS (it runs too hot wihtout power saving).

                    Comment


                    • #50
                      Originally posted by obino View Post
                      Thank you: indeed they all applied and now my laptop is usable with KMS (it runs too hot wihtout power saving).
                      Great
                      I was surprised by how well these new patches keep the beast from overheating my notebook. A big thank you to all the devs, and gods and geniuses who are working on the open source drivers. Really.

                      I was wondering... are you using an rc3 or rc4 tarball of linux, or an updated git version? Did you apply 0001-drm-radeon-kms-use-wait-queue-events-for-VBLANK-sync.patch (another patch, different from the one you jumped before)?

                      Thank you.

                      Comment

                      Working...
                      X