Results 1 to 10 of 26

Thread: Nouveau Lights Up The GK106 Kepler

Threaded View

  1. #20
    Join Date
    Feb 2012
    Posts
    373

    Default

    Quote Originally Posted by crazycheese View Post
    If you are so sure of their words, just go ask nvidia now - "When does this "bug" gets resolved".
    If they say "never", don't make confused face.
    There is no "bug". A bug would be a feature not working correctly. But what we have here is a feature (specifically overclocking) not being there at all, because the devs consciously decided not to implement it. Big difference.

    Quote Originally Posted by crazycheese View Post
    Reclocking is ability to change clocks. Its absent, see above.
    Reclocking is switching between pre-programmed performance levels. It's there in the nvidia driver. Beginnings of it are in nouveau as well, but to provide it fully, the nouveau devs will need to do what they need to do for any other feature - reverse-engineer it.

    Quote Originally Posted by crazycheese View Post
    No, they are not "doing nothing". Doing nothing means - continue actions.
    Err, what? Doing nothing means... doing nothing.

    Quote Originally Posted by crazycheese View Post
    But what they did, they cut and removed features and driver that could lead to faster nouveau development, and ONLY those.
    They stopped developing the nv driver. But they didn't "cut" or "remove" anything from it.


    Quote Originally Posted by crazycheese View Post
    Overclocking has everything to do with reclocking!
    Reclocking is switching between pre-programmed performance levels. Overclocking is setting freqs beyond those pre-programmed ones. The two need to be implemented separately.

    Quote Originally Posted by crazycheese View Post
    The reclocking logic is working within the driver!
    Wait, wait, didn't you say before reclocking is absent? You did, I even quoted it! Who's the troll here, I wonder.

    Quote Originally Posted by crazycheese View Post
    They removed only the coolbits - ability to manually change/force clocks.
    Again, they didn't "remove" it, they never implemented it. And no, your conspiracy theory is not the only reason for that.

    Overclocking is dangerous. Today's GPUs are beasts that produce a lot of heat, that have different parts clocked differently at a given moment, and those clocks are dynamically changing all the time. To mess with that and keep stability of the whole thing requires a very, very careful implementation. The Nvidia devs decided it would take too much time to tackle this challenge, so they decided to simply not tackle it.
    Last edited by Gusar; 12-15-2012 at 07:18 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •