Page 5 of 5 FirstFirst ... 345
Results 41 to 46 of 46

Thread: AMD Kaveri: Gallium3D vs. Catalyst Drivers

  1. #41
    Join Date
    Oct 2008
    Posts
    3,036

    Default

    Quote Originally Posted by HokTar View Post
    Rakot has already posted all the answers to your questions in #17:
    No he hasn't. In fact, that's the post i was referring to.

    Is Michael Danzer's radeonsi code referenced there public, or not? That's my question.

  2. #42
    Join Date
    Dec 2007
    Posts
    2,329

    Default

    Quote Originally Posted by smitty3268 View Post
    No he hasn't. In fact, that's the post i was referring to.

    Is Michael Danzer's radeonsi code referenced there public, or not? That's my question.
    It will be available when he's feels the code is ready for a wider audience.

  3. #43
    Join Date
    Dec 2009
    Posts
    338

    Default

    Quote Originally Posted by smitty3268 View Post
    No he hasn't. In fact, that's the post i was referring to.

    Is Michael Danzer's radeonsi code referenced there public, or not? That's my question.
    Ah, you didn't mention you were only interested in radeonsi...

  4. #44
    Join Date
    Jan 2009
    Posts
    614

    Default

    Quote Originally Posted by HokTar View Post
    So to me it seems like development slowed done since the dpm and uvd push. More precisely:
    ...
    - Marek has almost fewer mesa commits than in his worst exam period.
    The commit count doesn't really tell much about somebody's performance. The only thing you can tell from that is "the guy is doing something". It's generally easier to make a lot of commits when a driver is incomplete and buggy, which is no longer the case even with radeonsi. I also used to pick the easy tasks first and I'm afraid there are really not many of them left.

  5. #45
    Join Date
    Dec 2009
    Posts
    338

    Default

    Quote Originally Posted by marek View Post
    The commit count doesn't really tell much about somebody's performance. The only thing you can tell from that is "the guy is doing something". It's generally easier to make a lot of commits when a driver is incomplete and buggy, which is no longer the case even with radeonsi. I also used to pick the easy tasks first and I'm afraid there are really not many of them left.
    This was also one of my possible conclusions:

    Quote Originally Posted by HokTar View Post
    ...
    Or maybe he is just working on more complicated stuff that needs more time. Clearly, I can't tell from the outside and this is why I asked. Please do _not_ misinterpret this, I am merely curious.
    ...
    As mentioned earlier: please do not be offended! I love and appreciate your work!
    I merely wanted to clarify why your activity decreased. (BTW, same seemed to be true to Christian, too.)

    Please keep the great stuff coming and have fun at it!

  6. #46
    Join Date
    Jan 2009
    Posts
    614

    Default

    One part of the reason there are less commits for the radeonsi Mesa driver is that it's our first driver which has its shader backend officially in LLVM, and more time spent with LLVM means less time spent with Mesa.

Posting Permissions

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