Results 1 to 10 of 10

Thread: SUSE Loses Another Former RadeonHD Developer

  1. #1
    Join Date
    Jan 2007
    Posts
    14,218

    Default SUSE Loses Another Former RadeonHD Developer

    Phoronix: SUSE Loses Another Former RadeonHD Developer

    Matthias Hopf, a SUSE developer working on the X11 stack for the past seven years and one of the original xf86-video-radeonhd driver developers, has left the company...

    http://www.phoronix.com/vr.php?view=OTg2NQ

  2. #2
    Join Date
    Dec 2008
    Posts
    139

    Default

    Who cares?

    RadeonHD has been dead for a while.

  3. #3

    Default

    I had no idea SUSE had PhDs working on open source projects. That in itself is news:

    http://www.mshopf.de/

  4. #4
    Join Date
    Oct 2007
    Posts
    1,243

    Default

    Quote Originally Posted by LLStarks View Post
    Who cares?
    RadeonHD has been dead for a while.
    Having used radeonhd in its heyday, I care (and Mathias contributed to other projects as well). It is nice to hear that he will have a job in the academic world where he will have a chance to spark the next generation of Linux video hackers. I wish him well.

  5. #5
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by LLStarks View Post
    Who cares?

    RadeonHD has been dead for a while.
    i care to!... the radeonHD was really cool,,, and they only lag on support!

    Bridgman was one of the man how kill the radeonHD

    because he prefer more in-house developing means today more amd dudes do the ground work and the documentation and spec follow.

    back in the radeonHD time the Spec was first and after that they write the driver clean room.

    clean room mean the "Bridgman" version isn't clean room the Bridgman way is to have full access to the catalyst source code and internal secret documentation.

    one of bridgman's job is to make sure secret stuff be secret in the future.

    mean bridgmans job is to make sure the firmware stay closed and the UVD crypto internals stay closed and the ATOM-Bios stay closed!

    because an FIREGL card compared to an normal cheap card is only 2 thinks: different driver OpenGL-optimations AND AtomBIOS settings.

    the RadeonHD hurt this unwriten LAW because they don't use the ATOM-BIOS means in the RADEON-HD world every cheap radeon card is a FIREGL card!

    in an real free world there are no "fireGL" or "Quadro" and no AtomBIOS and no FIRMWARE and no secret UVD crypto unit to force the DRM.

    Bridgman is the Economic Hitman manager to make sure no unwriten rule "FireGL"-"Atom-Bios"-"UVD-DRM"-"Firmware" are ever be hurt.

    the open-source driver is fine if they don't touch this rules.

  6. #6
    Join Date
    Oct 2007
    Posts
    1,243

    Default

    Quote Originally Posted by Qaridarium View Post
    i care to!... the radeonHD was really cool,,, and they only lag on support! Bridgman was one of the man how kill the radeonHD because he prefer ..
    I stopped reading right about there

  7. #7

    Default

    Matthias Hopf will be at XDC2011 Chicago in just over one week. Along with Hopf there will be his former colleagues Egbert Eich and Luc Verhaegen of the defunct RadeonHD project for the X.Org Developers' Conference.
    So after RadeonHD went defunct, did they ever use their expertise and contribute to the radeon driver? If not, why not?

  8. #8
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by DanL View Post
    I stopped reading right about there
    reading is not the interesting part.
    '
    write your personal trueness story about this tropic i will read it

  9. #9
    Join Date
    Apr 2010
    Posts
    1,946

    Default

    Quote Originally Posted by Qaridarium View Post
    i care to!... the radeonHD was really cool,,, and they only lag on support!

    Bridgman was one of the man how kill the radeonHD

    because he prefer more in-house developing means today more amd dudes do the ground work and the documentation and spec follow.

    back in the radeonHD time the Spec was first and after that they write the driver clean room.

    clean room mean the "Bridgman" version isn't clean room the Bridgman way is to have full access to the catalyst source code and internal secret documentation.

    one of bridgman's job is to make sure secret stuff be secret in the future.

    mean bridgmans job is to make sure the firmware stay closed and the UVD crypto internals stay closed and the ATOM-Bios stay closed!

    because an FIREGL card compared to an normal cheap card is only 2 thinks: different driver OpenGL-optimations AND AtomBIOS settings.

    the RadeonHD hurt this unwriten LAW because they don't use the ATOM-BIOS means in the RADEON-HD world every cheap radeon card is a FIREGL card!

    in an real free world there are no "fireGL" or "Quadro" and no AtomBIOS and no FIRMWARE and no secret UVD crypto unit to force the DRM.

    Bridgman is the Economic Hitman manager to make sure no unwriten rule "FireGL"-"Atom-Bios"-"UVD-DRM"-"Firmware" are ever be hurt.

    the open-source driver is fine if they don't touch this rules.
    Yeah, I became same opinion after he started taking arguments to prevent acceleration the driver development instead of being initiative.
    The positive thing is that he makes sure the driver is legally clean, the negative is that the driver is doomed to be second class for ever. It wonīt match fglrx, not in a year, not in 10 years, never.
    Once any serious improvements in opensource driver happen, they will ported to fglrx. But fgrlx critical optimisations will never be present in opensource.
    Do you think opensource driver lack of speed is due to resorting to atombios? I hate the whole thing about firegl, the approach is completey rubbish. Why not associate the price exlusively with priority support? Why not be able to register the card and recieve priority support from AMD instead of selling hardware? Why not charge for something REAL instead behaving like microsoft?

  10. #10
    Join Date
    Oct 2008
    Posts
    151

    Default

    Quote Originally Posted by Qaridarium View Post
    back in the radeonHD time the Spec was first and after that they write the driver clean room.

    clean room mean the "Bridgman" version isn't clean room the Bridgman way is to have full access to the catalyst source code and internal secret documentation.
    Neither is "clean room" implementation because either those writing the spec or those writing the code are under contract with AMD and bound by all their agreements. A real clean room implementation would take two groups, BOTH outside AMD. One group would have to reverse engineer the hardware and write a thorough specification free of any copyrighted material, the other group must be "untainted" and implement that specification. If you depend on Bridgman in any way, then it's not clean room.

Posting Permissions

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