Announcement

Collapse
No announcement yet.

This Is What Started AMD's Open-Source Strategy

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

  • V!NCENT
    replied
    Originally posted by pingufunkybeat View Post
    See, now you understand why it's difficult.
    No I don't, because most of that list is exposing a power profile option. KDE/Gnome/whatever can read the battery and expose a switch widget so that these two can tell the driver what needs to be done.

    What the driver should be able to do is:
    -Recognise chip;
    -Know its capabilities;
    -Translate this knowledge to clocking.

    Dynpm already does what you expect in the free driver.
    I don't know why it's making my fan scream all the time. At least with Fedora 15 KDE spin (yum upgraded). But either Fedora or 'RadeonFLOSS' or a bit of both are doing it wrong.

    Now it only needs several million lines of code to do it better.
    Look, I would like to have semi-perfect/perfect power management, but I'm satisfied if it would just largely work and devs would focus to improve much needed stuff in other areas.

    While I can totaly live without accelerated video, I'm guessing it would be better for my batterylife is it was accelerated and thus having a much bigger improvement in power consumption.

    Leave a comment:


  • pingufunkybeat
    replied
    Originally posted by V!NCENT View Post
    Given that I am a user, I'm expacting from AMD:
    -Efficient hardware amount of calculation per wattage (nothing to do with software);
    -Clock speed based on load. I'm expecting low resource consumption when using my 3D desktop, while a neckbreaking clockspeed when doing load intensive stuff like gaming;
    -My fan to rotate at constant speeds for a while, because if it doesn't do that, then I keep noticing that it runs all the freaking time.

    I also expect three performance modes to block the GPU from sucking my battery dead;
    -Power saving (enough for desktop usage);
    -Balanced (automatic switching between power saving and performance when needed);
    -Performance (always working for me at the highest possible speed);

    I want my laptop to be Balanced when not below 1/7th of the battery and Power saving once it hits the 1/7th mark. My desktop should always be balanced.

    Performance is for when I want my PC to be responsive at all times.
    See, now you understand why it's difficult.

    Dynpm already does what you expect in the free driver.

    Now it only needs several million lines of code to do it better.

    Leave a comment:


  • AnonymousCoward
    replied
    Originally posted by bridgman View Post
    Yep, and IIRC this is pretty much what you get from the proprietary driver (which is what "comes from AMD")
    But the proprietary driver doesn't do suspend-resume, which is kind of an essential feature for a laptop. So whatever driver you choose, you're screwed one way or another.

    Originally posted by bridgman View Post
    In the open source driver (which "comes from the community with help from AMD") there's still a lot of work to be done.
    Ditto for the proprietary driver.

    http://ati.cchtml.com/show_bug.cgi?id=135
    http://ati.cchtml.com/show_bug.cgi?id=153
    http://ati.cchtml.com/show_bug.cgi?id=199

    Leave a comment:


  • bridgman
    replied
    Yep, and IIRC this is pretty much what you get from the proprietary driver (which is what "comes from AMD") although I don't know if it automatically switches to a more miserly mode as the battery level drops.

    In the open source driver (which "comes from the community with help from AMD") there's still a lot of work to be done.

    Leave a comment:


  • V!NCENT
    replied
    Originally posted by pingufunkybeat View Post
    Because users expect maximum performance with the minimum power consumption. It's easy to clock the card up or down, but to clock it up or down just the right amount that it uses little power, and the user does not notice anything, that's a lot of optimisation, and it has to be implemented all over the driver.
    Given that I am a user, I'm expacting from AMD:
    -Efficient hardware amount of calculation per wattage (nothing to do with software);
    -Clock speed based on load. I'm expecting low resource consumption when using my 3D desktop, while a neckbreaking clockspeed when doing load intensive stuff like gaming;
    -My fan to rotate at constant speeds for a while, because if it doesn't do that, then I keep noticing that it runs all the freaking time.

    I also expect three performance modes to block the GPU from sucking my battery dead;
    -Power saving (enough for desktop usage);
    -Balanced (automatic switching between power saving and performance when needed);
    -Performance (always working for me at the highest possible speed);

    I want my laptop to be Balanced when not below 1/7th of the battery and Power saving once it hits the 1/7th mark. My desktop should always be balanced.

    Performance is for when I want my PC to be responsive at all times.

    Leave a comment:


  • bridgman
    replied
    Originally posted by pingufunkybeat View Post
    It's easy to clock the card up or down
    That's kinda what we were thinking going into the project (it was supposed to be one of the easier parts, not even mentioned in anyone's plans), but it didn't work out that way
    Last edited by bridgman; 19 September 2011, 03:11 PM.

    Leave a comment:


  • pingufunkybeat
    replied
    Originally posted by V!NCENT View Post
    But can anyone explain to me why the power management is such a freaking pain?
    Because users expect maximum performance with the minimum power consumption. It's easy to clock the card up or down, but to clock it up or down just the right amount that it uses little power, and the user does not notice anything, that's a lot of optimisation, and it has to be implemented all over the driver.

    Leave a comment:


  • Emyr
    replied
    Originally posted by V!NCENT View Post
    Sencor: "It's coled up in here main, give me some heat bitch ass drivah dude"
    Driver: "Aight... GPU, clock this up though da roof!"
    GPU: "Aaaaaight... 600 extra megaHERTZ, baby! BOOM!"
    Flexible clockspeed = killer driver feature. Nice GUI for config & monitoring makes it a winner.

    Leave a comment:


  • Melcar
    replied
    If I am not mistaken, the hard part is having to deal with the memory.

    Leave a comment:


  • V!NCENT
    replied
    Novell: "Yo 'sup AMD, yo dawg, G. We think we can bake them open source driver with da UVD, x264, dual display and 3D OpenGL in nine dev months from scratch 'n shit. 2D is just automatically going to work, because we have made them 3D engine work already, dawg. Let's blow this bitch!"
    AMD: "OK."
    V!NCENT: "What the f-...?!?!?!?!?!"


    But can anyone explain to me why the power management is such a freaking pain?
    You'd think it would go like this:

    Driver: "'Sup GPU, what's yo number, dawg?"
    GPU: "r500 homey... represent!"
    Driver: "Whats da power profile, KDE?"
    KDE: "High performance, g"
    Driver: "Aigh-aight. What's da max temp on that one, lookup-table-g"
    Loockup-table: "120 bitchin' degrees up in this mofo... Baby's sweeet!"
    Driver: "Aight, so what's the temp sencor?"
    Sencor: "It's coled up in here main, give me some heat bitch ass drivah dude"
    Driver: "Aight... GPU, clock this up though da roof!"
    GPU: "Aaaaaight... 600 extra megaHERTZ, baby! BOOM!"
    Driver: "That's how we roll! What's the temp, G?"
    Sencor: "It's getting hot in here, so take-"
    Driver: "OK, clock down, baby"
    GPU: "Word!"

    No?

    Leave a comment:

Working...
X