Announcement

Collapse
No announcement yet.

Open-Source 2D, 3D For ATI Radeon HD 5000 Series GPUs

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

  • etnlWings
    replied
    Well that reply went awfully off-track.

    Leave a comment:


  • allquixotic
    replied
    Originally posted by Wingfeather View Post
    Does anyone know what the plan is (if there is one!) for continued development on this? I just checked the evergreen_accel branch and it appears there hasn't been a commit for 9 days.

    In face of the (seemingly unexpected) corruption and crashes, is it still the case that the AMD guys are being moved off Evergreen and onto HD6000?
    Most significant changes the ATI guys make to their open source driver have to go through legal red tape. This red tape takes many times longer than actually writing the code, from what I hear. It's possible they have many fixes queued up but are waiting for them to be cleared.

    I think the system is broken, TBH. ATI thinks their own 3d driver algorithms are "intellectual property". They're mathematics for crying out loud. This is another instantiation of the Bilski debate, right here in our driver.

    I would rather that ATI go ahead and commit un-obfuscated drivers that contain the most maintainable and efficient algorithms they are aware of to provide the required functionality, with no regard to how much information about the hardware it potentially exposes. It might save Nvidia a week or two on figuring out what ATI is doing, but I have no doubt that if Nvidia really feels that ATI has techniques they lack, they've already taken apart a dozen or more HD5870s in their office, and run a $10,000/license disassembler on the Windows driver.

    It's the kind of double-tongued scenario that we have with most corporate-controlled "openness". They play the openness for the PR and approval of their customers, but it's really a sham, because they intentionally censor and filter everything before they "open" it up. In this case, it's not about the public being withheld information, but rather, correct, efficient, and timely drivers.

    And if you disagree with the above sentiment, then I expect that the asymptotic performance of Mesa3D on Radeon hardware will approach the performance of fglrx within 2% or so in the long run (or hey, even exceed fglrx performance, since you don't have to go through an abstract kernel interface like the one fglrx has). I'll be waiting for you to show me when relative performance parity has been reached - on any radeon hardware. Any at all.

    Just think: if there were no clever algorithms arms race between Nvidia and ATI, they would actually have to compete on more difficult terrain, like customer service, timeliness and license of drivers, price, and hardware bells and whistles. They would still be motivated to develop innovative algorithms (or at least use the ones others have developed), because as soon as they let their guard down, their cards would immediately get outperformed by the competition, and they'd have to find a way to make up for it. And they could still use timing as a way to gain a "landslide" market share over the competition: make a whole bunch of new cards, push out a great new driver with innovations, customers realize the superior solution and buy it... by the time your competitor has figured out what you've done to beat them, then make a release of it, you've already made your sales.

    Of course it makes sense to keep the gory details of the chip design secret, but I think the discrepancy between the closed and open source driver performance is not about that, but rather about software algorithms. Again, Bilski.

    Bring down the iron curtain and give us true openness; cut out the red tape.

    Leave a comment:


  • Wingfeather
    replied
    Does anyone know what the plan is (if there is one!) for continued development on this? I just checked the evergreen_accel branch and it appears there hasn't been a commit for 9 days.

    In face of the (seemingly unexpected) corruption and crashes, is it still the case that the AMD guys are being moved off Evergreen and onto HD6000?

    Leave a comment:


  • monraaf
    replied
    Originally posted by bridgman View Post
    OK, that seems like a useful clue. Do you still get hangs eventually when running the open drivers after fglrx ?
    No, for as far as I have tested it I haven't seen any hangs after that.

    Which GPU are you using ?
    This is on a HD 5750.

    Leave a comment:


  • nanonyme
    replied
    (and really, reopening bugs on different issues is a bad habit)

    Leave a comment:


  • nanonyme
    replied
    How about running it with Valgrind if that segfault relates to your case also?

    Leave a comment:


  • rohcQaH
    replied
    I hijacked this report for xv:
    https://bugs.freedesktop.org/show_bug.cgi?id=29788

    I tried to write a simple testcase that'd show the gfx corruption I mentioned, but after stripping imagemagick down as far as I could, the result was an uncorrupted screenshot. oops.

    btw:
    Originally posted by monraaf View Post
    It seems that I have to run fglrx first to set the GPU to a sane state before I can use any of the open source acceleration stuff.
    hasn't been a problem for me, the OSS drivers work equally well (or not well) after a cold boot.

    Leave a comment:


  • nanonyme
    replied
    Have you already filed a bug on your problems, btw?

    Leave a comment:


  • rohcQaH
    replied
    I was using the latest mesa git and the latest stable kernel (2.6.35). It's supposed to work with .35, so I don't want to risk further trouble by using a .36-RC-kernel.

    Besides, the trouble in 2d-land certainly isn't related to mesa.

    Leave a comment:


  • nanonyme
    replied
    Very much sounds like your kernel and Mesa aren't compatible with each other. "forbidden register" is a good hint of this. There's security functionality in kernel DRM, afaik mostly written by glisse, that causes that kind of stuff to be outputted. If the register should be usable, updating kernel might fix it. If not, updating Mesa might fix it. But since you don't know, could as well update both.

    Leave a comment:

Working...
X