Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 35

Thread: Open-Source Radeon HD 7000 Series Still Lacking

  1. #21
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,544

    Default

    That's like concluding we will support UVD in the open drivers because we support most of the other blocks. Reasonable if you don't look too closely.

    But very clear

  2. #22
    Join Date
    Nov 2009
    Posts
    101

    Default

    Quote Originally Posted by bridgman View Post
    ?? NI support has been there for a year or more. Trinity support has been out for a few months and that's based on NI.
    Sorry, I meant SI.

  3. #23

    Default

    Quote Originally Posted by barkas View Post
    it did not support gnome 3 for 4 months straight after release
    Not AMD fault, but AMD add workaround to driver anyway.
    Quote Originally Posted by barkas View Post
    crashed when I started xbmc
    Where we may look at XBMC crashlog and core dump?
    Quote Originally Posted by barkas View Post
    Not to mention that xvba just does not play back some videos it does fine in windows.
    That was changed.

    Anything else?

  4. #24
    Join Date
    Aug 2007
    Posts
    6,646

    Default

    Well as long as fglrx runs you can use the aticonfig command to enable h264 l5.1. but xbmc fernet menta branch is currently everything else than stable - especially when you dont use it fullscreen only but windowed or when you switch between both ways using \. do you try xbmc fm git code often?

  5. #25
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,283

    Default

    I find it curious that the AMD people imply they have some inside info on Intel's discrete efforts. What makes you think the hypothetical GPU would not be open, or that Knight's Corner will not have the rest open-sourced too once it actually starts selling a bit?

    If you're referring to the currently not-perfect GCC support for it, I find it likely that will change in the future.

  6. #26
    Join Date
    Jun 2012
    Posts
    44

    Default

    Quote Originally Posted by bridgman View Post
    ?? The topic was newly introduced GPUs, specifically SI, not older GPUs moved to a legacy branch.
    That is what I am referring to. My HD7xxx based card. When my HD4xxx card failed I needed to upgrade. Now with a brand new card with less power than my old GForce3 not because of the hardware but the drivers. The blob might be the greatest thing ever on RedHat5. Not sure. But it is useless on FC18. Sure AMD doesn't want to support some thing so bleeding edge and I don't blame them. But no one is asking them to. What people are asking for is documentation. With out it the HD7xxx is just one step up from a software frame buffer device. I don't understand why the AMD people are shocked that Linux people might not want to pay $$$ for bleeding edge features they are never going to get to use. Actually most things like audio over hdmi isn't exactly bleeding edge any more. Releasing documentation should have been of the process of coming to market, not an after thought.

  7. #27
    Join Date
    Oct 2008
    Posts
    3,219

    Default

    Quote Originally Posted by curaga View Post
    I find it curious that the AMD people imply they have some inside info on Intel's discrete efforts. What makes you think the hypothetical GPU would not be open, or that Knight's Corner will not have the rest open-sourced too once it actually starts selling a bit?

    If you're referring to the currently not-perfect GCC support for it, I find it likely that will change in the future.
    As I recall, Intel was asked whether Larrabee graphics drivers would be open sourced, and they refused to answer.

    That's not to say they wouldn't have been, but it's completely fair to note that when people are on here claiming that they would have.

  8. #28
    Join Date
    Nov 2009
    Posts
    101

    Default

    Quote Originally Posted by RussianNeuroMancer View Post
    Not AMD fault, but AMD add workaround to driver anyway.Where we may look at XBMC crashlog and core dump?That was changed.

    Anything else?
    Everything about this answer is wrong. Especially the attitude.

    It IS AMDs fault if it is the only driver that does not work in gnome3.

    I don't have that crashdump anymore, it's been a while since then, but I do not doubt that you can still get it to crash if you try.

    Yeah it was maybe changed, ignoring the fact that VDPAU worked fine out of the box and we're still struggling with xvba and that you have to do some very badly documented things and use some very bleeding edge software to get it to work.
    Last edited by barkas; 07-01-2012 at 06:01 AM.

  9. #29

    Default

    Quote Originally Posted by barkas View Post
    It IS AMDs fault if it is the only driver that does not work in gnome3.
    Do you read comment 14 of this bugreport carefully?
    Quote Originally Posted by barkas View Post
    ignoring the fact that VDPAU worked fine out of the box
    No, I doesn't. I just said "That was changed".
    Quote Originally Posted by barkas View Post
    and we're still struggling with xvba and that you have to do some very badly documented things and use some very bleeding edge software to get it to work
    This is also going to change. When XBMC-XvBA Team patches will be accepted by upstream ffmpeg, any ffmpeg-based application will be capable of using XvBA.
    HWUVD_H264Level51Support probably require wide testing before going to be enabled by default.

  10. #30
    Join Date
    Feb 2009
    Posts
    165

    Default

    Quote Originally Posted by barkas View Post
    It IS AMDs fault if it is the only driver that does not work in gnome3.
    Seriously? What kind of logic is this?
    So lets imagine you're the only one in your family who doesn't do drugs, you're automatically the one doing it wrong!?

    lol...

Posting Permissions

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