Announcement

Collapse
No announcement yet.

Some Good & Bad News For The Nouveau Driver

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

  • r1348
    replied
    Originally posted by 0e8h View Post
    It goes to show that the programming is so poor for the non-proprietary drivers as they should be lighting speeds ahead whilst they aren't doing all the features. Other words if a open source driver is only doing vectors and the proprietary-driver is doing vectors and buttering bread, then the former should be faster.

    The non-proprietary coders must be using bad kernel techniques, or not using proper hardware abilities.

    Get the vector speeds first, then start adding the buttered bread later else your project is pointless if it's going to be always slow!!!
    Have you ever wrote a graphical driver? Because you appear to have no clue about it.
    How are the nouveau devs supposed to make a performant driver without any proper documentation? Basically there's no deterministic way to foresee the performance of certain code paths over others, it's a matter of trial and error, which requires massive testing time.
    Now, as far as I know, apart from one dev, all nouveau driver work is done by volunteers, so feel free to contribute your performance improvements that you for sure keep in your private branch...

    Leave a comment:


  • smitty3268
    replied
    Originally posted by 0e8h View Post
    your project is pointless if it's going to be always slow!!!
    You spouted an awful lot of nonsense here, but i'm just going to respond to this one point. If the driver is just fast enough to display a composited desktop like Compiz/Kwin and can do nothing more complicated than that, it's already an extremely useful project. Speed is most definitely less important than other things, like stability, for example.

    And if you don't like the driver, then don't use it. No one's forcing you.

    Leave a comment:


  • smitty3268
    replied
    It doesn't appear to me that the Nouveau driver is doing any better than the radeon one, it's just that you benchmarked slower cards so the CPU limitations you are hitting with both just appear to be more of a problem on the faster cards.

    Leave a comment:


  • blackshard
    replied
    Originally posted by 0e8h View Post
    It goes to show that the programming is so poor for the non-proprietary drivers as they should be lighting speeds ahead whilst they aren't doing all the features. Other words if a open source driver is only doing vectors and the proprietary-driver is doing vectors and buttering bread, then the former should be faster.

    The non-proprietary coders must be using bad kernel techniques, or not using proper hardware abilities.

    Get the vector speeds first, then start adding the buttered bread later else your project is pointless if it's going to be always slow!!!
    Maybe the point of opensource drivers is not speed.

    However, about the conclusion of the article, compraring relative speed between ati and nvidia opensource vs blob implementation is an apple vs orange comparison and no conclusion can be taken.

    Leave a comment:


  • saski
    replied
    given the fact that the nouveau driver is being developed without any technical documentation support or help from NVIDIA and with a much smaller headcount of developers this performance result is absolutely awesome!

    great work folks! keep it up!

    Leave a comment:


  • 0e8h
    replied
    Originally posted by Shining Arcanine View Post
    How is being within 50% of the proprietary driver's performance good? That is not acceptable for gamers.
    I agree. Something is seriously wrong. People maybe willing to use a modular driver model if is was say 80% of another non-modular.

    The programmers need to step back ten steps and looks at their project and see what they are overlooking or what needs to happen to fix the direction.

    Should the driver stick to 2d, not 3d?

    Leave a comment:


  • 0e8h
    replied
    It goes to show that the programming is so poor for the non-proprietary drivers as they should be lighting speeds ahead whilst they aren't doing all the features. Other words if a open source driver is only doing vectors and the proprietary-driver is doing vectors and buttering bread, then the former should be faster.

    The non-proprietary coders must be using bad kernel techniques, or not using proper hardware abilities.

    Get the vector speeds first, then start adding the buttered bread later else your project is pointless if it's going to be always slow!!!

    Leave a comment:


  • r1348
    replied
    Originally posted by Shining Arcanine View Post
    How is being within 50% of the proprietary driver's performance good? That is not acceptable for gamers.
    Are you even aware on what and how nouveau is?

    Leave a comment:


  • not.sure
    replied
    Originally posted by Shining Arcanine View Post
    How is being within 50% of the proprietary driver's performance good? That is not acceptable for gamers.
    You must be new here.

    Leave a comment:


  • Shining Arcanine
    replied
    How is being within 50% of the proprietary driver's performance good? That is not acceptable for gamers.

    Leave a comment:

Working...
X