Announcement

Collapse
No announcement yet.

Nouveau Lights Up The GK106 Kepler

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

  • phoronix
    started a topic Nouveau Lights Up The GK106 Kepler

    Nouveau Lights Up The GK106 Kepler

    Phoronix: Nouveau Lights Up The GK106 Kepler

    Red Hat's Ben Skeggs pushed out new code this morning into the Nouveau DRM driver repository. In addition to some video BIOS work and other changes, initial support for the NVIDIA GK106 GPU was pushed into this reverse-engineered open-source driver...

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

  • crazycheese
    replied
    Originally posted by Gusar View Post
    Dafuq?

    I don't have any "goal". You *are* wrong. You are mixing up reclocking and overclocking, when they're two different things, requiring different handling. It's in *your* interest to accept that, but if you instead choose to remain ignorant...
    Lolwut? I am incorrect in everything because I define reclocking as RE[1]CLOCKING[2]?!
    Gusar, you forgot to "edit the internet" before trolling me

    You know exactly what I meant, when I said:
    Originally posted by crazycheese View Post
    The reclocking logic is working within the driver! Even for newer nvidia GPUs. They removed only the coolbits - ability to manually change/force clocks. The ONLY reason to do that is to prevent projects like nouveau to detect GPU state magic when manually changing clocks, including automated way - and as such to reverse and implement own clock change tool/logic.
    Its like car with automatic shift. There is no shift outside, but there is shifting inside. And you can't control it and its hidden deeply within the obfuscated logic.
    Yet you try contradict me
    Your are either stupid or purposely lying, both kindergarten - for children or big children. Take your pick.
    Maybe, after you "edit the internet" on reclocking definition, and after trolling Michael Larabel, you go troll car industry.

    Leave a comment:


  • Gusar
    replied
    Originally posted by crazycheese View Post
    Ha, your goal is to make me admit something!
    Dafuq?

    I don't have any "goal". You *are* wrong. You are mixing up reclocking and overclocking, when they're two different things, requiring different handling. It's in *your* interest to accept that, but if you instead choose to remain ignorant...

    Leave a comment:


  • crazycheese
    replied
    Originally posted by Gusar View Post
    How typical. Instead of admitting you're wrong, you resort to this. Lame.
    Ha, your goal is to make me admit something! That means your head is already full, made up and predictable, and you are here not for questions, but for exclamations
    Well, I don't need anyone to bullshit me, thank you!

    Leave a comment:


  • Gusar
    replied
    Originally posted by crazycheese View Post
    Gusar, no need to write stupid child crap for me, go play in sand box!
    How typical. Instead of admitting you're wrong, you resort to this. Lame.
    Last edited by Gusar; 12-15-2012, 08:56 AM.

    Leave a comment:


  • crazycheese
    replied
    Originally posted by Gusar View Post
    *kindergarten*
    Gusar, no need to write stupid child crap for me, go play in sand box!

    Originally posted by Michael Larabel
    Nouveau Reclocking: Buggy, But Can Boost Performance
    What this new code allows for the NV50 hardware is to properly change the GPU core, graphics memory, and shader clock speeds in real-time along with the memory timings, voltage, and fan speed (though the power management itself is still premature and if manipulating the clocks it will just force the fan(s) to run at 100% speed).
    Go, troll Larabel
    Last edited by crazycheese; 12-15-2012, 08:27 AM.

    Leave a comment:


  • Gusar
    replied
    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.

    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.

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

    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.


    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.

    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.

    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, 08:18 AM.

    Leave a comment:


  • crazycheese
    replied
    Originally posted by Calinou View Post
    Overclocking has nearly nothing to do with reclocking.
    Overclocking has everything to do with reclocking!
    You can't overclock if your card can't reclock.
    You can't underclock if your card can't reclock.
    You can't even use your card properly, its like Geforce 1 era.

    Originally posted by Calinou View Post
    Overclocking can lead to overheat, which means less customers. That's why they removed it, don't blame them. The default clock set by NVIDIA is set for a reason.
    Common, quit being stupid please. Overclocking on windows is not affected. Preoverclocked cards are available. Overclocking and underclocking/undervolting is widely available and used everywhere. It belongs to same shelf as "tuning" the hardware for better needs. Only ready OEM solutions have all features stripped. Please think before you write, don't succumb to trolling. :/

    The reclocking logic is working within the driver! Even for newer nvidia GPUs. They removed only the coolbits - ability to manually change/force clocks. The ONLY reason to do that is to prevent projects like nouveau to detect GPU state magic when manually changing clocks, including automated way - and as such to reverse and implement own clock change tool/logic.
    Last edited by crazycheese; 12-15-2012, 07:32 AM.

    Leave a comment:


  • Calinou
    replied
    Overclocking has nearly nothing to do with reclocking.

    "No, they are not "doing nothing". Doing nothing means - continue actions. But what they did, they cut and removed features and driver that could lead to faster nouveau development, and ONLY those."

    Overclocking can lead to overheat, which means less customers. That's why they removed it, don't blame them. The default clock set by NVIDIA is set for a reason.

    Leave a comment:


  • crazycheese
    replied
    Originally posted by Gusar View Post
    It wasn't "disabled", they never implemented it. They decided not to, because their time is limited and they wanted to spend it on other stuff. I can search for the exact quote if you want to, it's somewhere at the nvnews forums.
    I don't judge by anything I am told, I judge by actions.
    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.

    Originally posted by Gusar View Post
    Now you're talking about reclocking, which is a totally different thing from overclocking. The card starting at the lowest clock is being done from a thermal standpoint, no connection to nouveau.
    Reclocking is ability to change clocks. Its absent, see above.
    That the cards starts at lowest clocks has no connection to any driver, it is to prevent user from having headaches due to spinning fans. It was fixed in GTX 2xx VGA BIOSes.

    Originally posted by Gusar View Post
    That's an interesting spin. But that's all it is - spin. Not providing info, whatever info, is not "hindering". It's doing nothing.
    No, they are not "doing nothing". Doing nothing means - continue actions. But what they did, they cut and removed features and driver that could lead to faster nouveau development, and ONLY those.

    Originally posted by Gusar View Post
    Also, they never planned to implement even basic 2d for Fermi in the nv driver, nothing to do with nouveau. I'm too lazy to go search for the exact mailing list posts, but they said implementing 2d accel would require accessing the 3d engine and they didn't want to expose anything about the 3d engine. Which makes sense, modern graphic cards don't have 2d engines anymore, and the nv driver never had anything about 3d engines in it.
    Yes the second part makes sense, but it makes little sense not to implement 2D. Because 2D over 3D texture was done since fix function GPUs were laid off, IMHO.

    Leave a comment:

Working...
X