Page 2 of 6 FirstFirst 1234 ... LastLast
Results 11 to 20 of 59

Thread: RadeonSI Gallium3D Gets New State Handling

  1. #11
    Join Date
    Jan 2009
    Posts
    1,706

    Default

    Quote Originally Posted by Veerappan View Post
    As was mentioned before. The Radeon drivers have added support for 9 years of hardware in the last 5 years. In the case of my radeon 4850, which I bought in Fall of 2008, it was 8+ months before a classic Mesa driver got usable 3D support (2D worked ok, but I ran Catalyst at the time). In the meantime, we've gotten a rock solid r300g driver, good quality r600g which needs performance optimization and some new OpenGL features, and now we're getting VDPAU/OpenCL/GLES and other features as well.

    .
    OpenCL is worked on but isn't vdpau stopped?? Or i missed something??

  2. #12
    Join Date
    Dec 2011
    Posts
    2,103

    Default Why?

    Why is it that with Intel there is support for the latest generation graphics even before its been sent to manufacturing?

    While with AMD, there is still no support even 6 months after its hit the shelves?

  3. #13
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,514

    Default

    Two part answer...

    One part is that different HW vendors don't make big architectural changes at the same time. A better comparison might be Trinity vs Ivy Bridge, both of which had support before launch, although as I understand it the Ivy Bridge changes were probably somewhere between Trinity and SI in complexity.

    Second part is that we've been catching up over the last 5 years (as a bunch of people have already mentioned) and are almost-but-not-quite caught up. SI was the first new GPU generation where we were able to get substantial work done before launch, but that still meant we were working almost a year behind Catalyst. The next generation will be the first where open source graphics driver development is able to run more or less in parallel with Catalyst development work -- agd5f already has initial kernel driver support written.

  4. #14
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    Quote Originally Posted by uid313 View Post
    Why is it that with Intel there is support for the latest generation graphics even before its been sent to manufacturing?

    While with AMD, there is still no support even 6 months after its hit the shelves?
    More people, no accumulated backlog to clear, and much earlier access to hardware prototypes/simulators.

    With AMD, the latter two are improving, but more manpower would help. It's hard to find good programmers who would make an immediate difference, though.

    I was hoping that there would be at least basic GL 2.1 + EXA support for SI by now. I wanted to buy a new card already in March, but I won't do it until the card works for everyday stuff (including basic GL and accelerated 2d).

  5. #15
    Join Date
    Jan 2009
    Posts
    466

    Default

    JB,

    How many OSS developers are working on the next generation architecture (9000 series for release in the 2014 timeframe)?

    There's two ways to arrive at a destination earlier. Leave earlier, and go faster.

    F

  6. #16
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,514

    Default

    You mean next-next, right ? Current gen is 7000, presumably next gen is 8000 and the one after that is 9000 ?

    Once we get past next-gen we'll be working in parallel with the Catalyst and diags teams. Starting earlier than them isn't really practical.

    Quote Originally Posted by pingufunkybeat View Post
    I was hoping that there would be at least basic GL 2.1 + EXA support for SI by now. I wanted to buy a new card already in March, but I won't do it until the card works for everyday stuff (including basic GL and accelerated 2d).
    Yep, that's what we were hoping for as well. The code has been written and published for a while, but it's hard to predict how long it will take for the last few "in theory we're programming it right but in practice something is obviously wrong" gotchas, although the range of variation goes down significantly if you are debugging the code early enough to lean on emulators and HW debug teams a bit.
    Last edited by bridgman; 07-24-2012 at 01:06 PM.

  7. #17
    Join Date
    Sep 2011
    Location
    Rio de Janeiro
    Posts
    202

    Default

    Quote Originally Posted by bridgman View Post
    You mean next-next, right ? Current gen is 7000, presumably next gen is 8000 and the one after that is 9000 ?

    Once we get past next-gen we'll be working in parallel with the Catalyst and diags teams. Starting earlier than them isn't really practical.



    Yep, that's what we were hoping for as well. The code has been written and published for a while, but it's hard to predict how long it will take for the last few "in theory we're programming it right but in practice something is obviously wrong" gotchas, although the range of variation goes down significantly if you are debugging the code early enough to lean on emulators and HW debug teams a bit.
    So we can expect out of the box support for "9000" series in 2014-ish? Seems like even catalyst team is behind lately, has VCE been enabled in windows?

  8. #18
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,182

    Default

    Quote Originally Posted by bridgman View Post
    Once we get past next-gen we'll be working in parallel with the Catalyst and diags teams. Starting earlier than them isn't really practical.
    Now if only the graphics drivers were GPL and not MIT

    Start earlier than Catalyst -> Cat people will look in the open code -> open code likely taints Cat -> Cat must be open-sourced.

  9. #19

    Default

    Quote Originally Posted by curaga View Post
    Now if only the graphics drivers were GPL and not MIT

    Start earlier than Catalyst -> Cat people will look in the open code -> open code likely taints Cat -> Cat must be open-sourced.
    This is wrong if you are 100% the copyright holder you can release the code as GPL and MIT and closed source without any problem.

  10. #20
    Join Date
    Jan 2009
    Posts
    466

    Default

    Quote Originally Posted by Figueiredo View Post
    So we can expect out of the box support for "9000" series in 2014-ish? Seems like even catalyst team is behind lately, has VCE been enabled in windows?
    While I don't expect OOTB support for 9000, it is good to know that the OSS team will be starting to ramp up at the same time fglrx is starting to ramp up. Unfortunately, and this is speculation, I fear that the hardware teams are so used to working with the catalyst team's processes that there will be some growing pains for the OSS team. True parity will likely never occur. That's OK though, as long as the OSS team can produce an acceptable driver in a reasonable amount of time.

    While a number of us complain that OSS isn't delivered as fast as FGLRX, what we're really trying to say is that we want an acceptable driver in a reasonable amount of time. The fact that FGLRX exists annoys us, because it reminds us constantly of what-could-have-been had AMD shared our utopian software development philosophy. Really, you just want your purchased product to work, and work now, and align with your philosophy.

    I'll be looking forward to AMD's 9000 offering. I hope that they can deliver a working OSS driver in an acceptable timeframe.

    F

Posting Permissions

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