Page 4 of 12 FirstFirst ... 23456 ... LastLast
Results 31 to 40 of 118

Thread: Bridgman Is No Longer "The AMD Open-Source Guy"

  1. #31
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,338

    Default

    Best regards to Bridgman. And welcome to the new public face slash general punching bag

  2. #32
    Join Date
    Oct 2009
    Posts
    15

    Default

    Why you keep calling him the last name only. Why don't you call simply John. John B., etc. Is too confusing?
    I think Johnny here has really nice name.

  3. #33
    Join Date
    Feb 2011
    Location
    Toronto, ON, Canada
    Posts
    31

    Default

    Quote Originally Posted by RussianNeuroMancer View Post
    Tim, congratulations! I hope you don't forget about XBMC-XvBA developers
    I haven't forgotten and am in the process of transitioning responsibility for the XvBA SDK to one of the developers on my (Embedded Linux) team which will help to get it back on track.

    Tim

  4. #34
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    884

    Default

    Good luck in your future endeavours John. Hopefully you'll stick around and keep enlightening us occasionally.

    Tim, welcome to the position and the forums. Hopefully you've got the patience to deal with some of the people we've got here

  5. #35
    Join Date
    Dec 2008
    Posts
    168

    Default

    Quote Originally Posted by bridgman View Post
    Not blind, but a lot of the work was less visible than usual. There were three big contributors to that :

    1. Moving to a new shader architecture (GCN), new memory management (GPUVM) and new shader compiler (llvm) at the same time. This was kind-of necessary but it meant that we had far more work in process where you couldn't see an obvious benefit. Using llvm was partly to build a good foundation for an open source OpenCL stack, and partly to get a more capable shader compiler into the graphics stack.

    2. Doing speculative development on the two remaining weak spots of the current driver stack -- power management and accelerated video decode. Historically there was so much catch-up work to be done that we focused development efforts in areas where we were pretty sure we would be able to release the resulting code, so there was little risk of wasted effort and (relatively) short delays between writing code and having the results publicly visible.

    In these last two areas we knew that the review/revise/repeat process would be a lot longer, but we reached the point where it made sense to dive in anyways. We had to write/debug a lot of code just to get the process going, so there was a bunch of work done there which hasn't shown you any real benefit yet.

    3. Making a big push to have launch-time open source support. This is the ultimate "developers do a lot of work but you don't see anything" investment because you don't see the results until closer to hardware launch date, but it is an important step.

    It's probably fair to say that more work has been done in the last year than any previous year, but relatively less of it has been immediately visible.
    You guys originally promised open-source release schedule parity with Windows in time for 8000 series. Not happening anymore?

  6. #36
    Join Date
    Jul 2010
    Posts
    449

    Default

    Quote Originally Posted by LLStarks View Post
    You guys originally promised open-source release schedule parity with Windows in time for 8000 series. Not happening anymore?
    I don't think they promised, I think they said "we should have" or "we hope to have".

  7. #37
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,578

    Default

    To be precise, this is the first new GPU generation where development work was able to start early enough to give us a good chance of having support ready in time for product launch. I think what we said was "we're planning for it" (aiming for it / expecting it / working towards it, whatever) and that hasn't changed.

    The obvious question is "why didn't you just start earlier before ?", and the answer is "because support for each new generation builds on support for the previous generation, so we need to finish initial support for the previous generation first".
    Last edited by bridgman; 09-20-2012 at 04:26 PM.

  8. #38
    Join Date
    Dec 2011
    Posts
    157

    Default

    Thank you John Bridgman for all your work, and your openness here!
    Welcome to Tim and good luck on helping us all

    (I actually registered an account here just to talk with John... I was just reading before...)
    Last edited by geearf; 09-20-2012 at 04:20 PM.

  9. #39
    Join Date
    Oct 2009
    Posts
    2,145

    Default

    Quote Originally Posted by twriter View Post
    I'm already here, just about 6,000 times less prolific than John.

    Tim
    So maybe you can answer the million dollar question then... UVD open source driver... when?

  10. #40
    Join Date
    Jan 2009
    Posts
    1,502

    Default Thanks Bridgman!

    Quote Originally Posted by phoronix View Post
    Phoronix: Bridgman Is No Longer "The AMD Open-Source Guy"

    After five years of the open-source AMD strategy, John Bridgman is no longer managing these efforts...

    http://www.phoronix.com/vr.php?view=MTE4ODU
    You had a tough, often times thankless job (at least on this side of the fence) but I appreciate your efforts to communicate and inform.
    Best of luck with the new gig!

    Best/Liam

Posting Permissions

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