Announcement

Collapse
No announcement yet.

"Ask ATI" dev thread

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

  • "Ask ATI" dev thread

    If you guys come up with the questions, I will get the answers - Michael
    Post any questions that you have for ATI fglrx devs here...

  • #2
    how can you guarantee any ati dev will answer them?

    all i care about is : (not really to the devs)
    > when can we expect the rest of the docs?

    Comment


    • #3
      What would be most interesting is "what are you working on for the next releases?", but they won't answer that.

      Comment


      • #4
        What apps/tools/games do the devs use for testing regressions and speed? In particular, has there any testing of wine wrt the awful performance noted by wine devs
        More like your video drivers broken / misconfigured. ATi's craft known to by
        buggy beyond repair.
        from http://bugs.winehq.org/show_bug.cgi?id=10487

        Any likelihood of AVIVO support?
        Last edited by hmmm; 11-21-2007, 04:59 PM.

        Comment


        • #5
          hotfixes?

          I wonder if there is any plans on having hotfixes in the future. For like bugs like soname and the memleak...

          Comment


          • #6
            My only question to the developers:

            Are you aware of the existing memory leak in 8.41, 8.42 and seemingly fglrx 7.11?

            That's about it. Xv works fine for me, as does all the other features I use. I just want to know that they know about said (fatal) memory leak.

            Comment


            • #7
              Besides other stupid issues with the driver: why are the FireGL ids removed when they could be patched back easyly? I think it should be the users choice which driver they want to use - even buggy ones. And another one: why not use lzma compression? I have sample scripts that can already repack any driver (with static decoder) and its size drops dramatically. Example:

              47667647 (100%) ati-driver-installer-7-11-x86.x86_64.run
              28335222 (59%) ati-driver-installer-7-11-x86.x86_64.run.lzma-static-decompressor
              Last edited by Kano; 11-21-2007, 05:38 PM.

              Comment


              • #8
                Why do the KB numbers in the driver's release notes not directly link to the KB articles?

                Why is the card state (sometimes?) not reinitialized on reboot:
                1. related to the vesa framebuffer console bug, when I reboot (via ctrl+alt+del) sometimes the 'dead' state that caused me to need to reboot persists forcing another restart
                2. possibly X.org's fault(?) upon reload of X.org/gdm I see a garbled version of the previous state of the screen (ie, what was shown before the reboot), then it loads as normal. Contrasted with windows where that doesn't happen. This happens in versions of the driver with or without the vesa framebuffer issue.

                How does the driver team ascribe priority to what will be developed in each release?

                What code management do they use and are team members allowed to keep private branches in order to target specific issues (like new kernel or X.org support)?

                Related to ZedDB's question:
                Are the devs regularly frustrated by having fixed issues but not being able to push them out to their users because of the dev cycle (or other restrictions) imposed by management?

                How much easier would development be if there were lower-end GPUs targeted specifically for linux (similar to the Intel GPU offerings)?

                Comment


                • #9
                  Simple question:
                  do you know of this bug? or you think you have fixed it as you've written in the release notes of 8.37.6?

                  bug link: http://ati.cchtml.com/show_bug.cgi?id=239

                  Comment


                  • #10
                    Question:

                    You just released the most useless driver update ever...
                    How does that make you feel?

                    Real/other question: Are you aware of the other MORE important bugs that need fixed like the memory leak?

                    Comment


                    • #11
                      Yeah, I got a question for ATI, what do they smoke? What do they do 8 hours a day 5 days a week and release a 3 bug fix release on the most simple things that could possibly be added to a release. I like AMD, I really do, but with all the outstanding issues and bugs in fglrx, they could only manage to fix 3 extremely minor issues over the course of a month?

                      I don't care if you have 1 or 3 guys working on that driver, 8 hours a day, 5 days a week, you can accomplish alot more than that. I almost think they are playing ping pong in the office. Going around with beer bongs and getting completely wasted then they sit down and well.. Okay! Time to get to work! Lets see... Oh yeah, we need to add 2.6.23 kernel support, okay, that should take us about a month to add that.

                      Now, you can say, well they are preparing for the now called 7.12 driver, I think thats bogus. So they're going to have everyone wait yet another month and don't even fix at least one major issue? We aren't concerned with new features at this point, we really could care less, we want bug fixes, and stable drivers. Something we honestly never had. Yeah now they can run pretty fast when they want to, but that doesn't solve the issue.

                      Alright I'm done venting. I still have faith in AMD, and we better see some decent results in the releases to come since they are hiring more people for their Linux driver development. Because if we see another release like this, I'm going to hold my end of the bargain and give Phoronix a video called "What happens when you have a ATI card and a baseball bat?". You want action, I'll dish it out in full. Haha.

                      Alright well anyway, I hope to see better releases from them in the future, this release was a joke. I think at this pace, the Open Source driver will pass fglrx in about a year to year in a half from now.
                      Last edited by Malikith; 11-21-2007, 10:07 PM.

                      Comment


                      • #12
                        @Malikith:
                        Did it ever come to your mind that there might be fixes, that are not listed in the changelog? I do know that *many* devs are rather sloppy when it comes to writing down the real changes for mundane stuff like a "changelog".

                        The problem is that users do not have a way to check if their problems are fixed when the changelog is this incomplete. I think one of the main problems AMD/ATI had so far was communication with the community. But I think the posts from Bridgman indicate some change in that area. The real things I would love to know are simple:

                        - Will there be an official bugtracker that gets frequented by the devs so that users do have a way to see if their problems are fixed?
                        - Will there eventually a more complete listing of the fixed/known problems? Currently the list is really abysmal.

                        Comment


                        • #13
                          Did it ever come to your mind that there might be fixes, that are not listed in the changelog? I do know that *many* devs are rather sloppy when it comes to writing down the real changes for mundane stuff like a "changelog".
                          i'd rather see super-detailed changelog even if it would contain boring stuff. they must have some SCM for their code - see how easy it is to make a detailed linux kernel changelog without too much work.

                          the only explanation for me is - they still have tons of problems with the new codebase, and trying to get it to compile (oh, and work ) takes lots of time.

                          Comment


                          • #14
                            Originally posted by yoshi314 View Post
                            the only explanation for me is - they still have tons of problems with the new codebase, and trying to get it to compile (oh, and work ) takes lots of time.
                            i think they are reverse-engeenering the nvidia driver trying to tailor it for ati card, cause i seriously doubt they realy can come up with they own bugfixes ..
                            Last edited by macmus; 11-22-2007, 05:58 AM.

                            Comment


                            • #15
                              I would like to know why the new driver (8.43.3 & 8.42.3) makes the screen go black for 2-3 secs when you start a video file (with or without compiz)? Is the driver switching screens when I runs a video?

                              Regards

                              André

                              Comment

                              Working...
                              X