Announcement

Collapse
No announcement yet.

HyperZ: Errata & The Catalyst Command Stream

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

  • HyperZ: Errata & The Catalyst Command Stream

    Phoronix: HyperZ: Errata & The Catalyst Command Stream

    Following yesterday's article about Radeon Gallium3D HyperZ support defeating open-source developers, Jerome Glisse has clarified the situation after trying to make this code work properly for more than a half-year...

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

  • #2
    Oh plz. Just show us some Pipeworks Hyper Dog beer to hint to us that HyperZ isn't dead yet.

    Also you need to find a beer with "fire" in the name to hint that fglrx is going open source

    Comment


    • #3
      http://eatingisntcheating.blogspot.c...agic-rock.html

      The future is uncertain...

      Comment


      • #4
        Originally posted by bridgman View Post
        Why is there a public erratum list for AMD cpus and not public erratum list for AMD gpus?
        In my point of view AMD do not act rational and logical.

        Maybe AMD should pay someone who can help them out with rational and logical thinking.

        Comment


        • #5
          We include the errata in the programming documentation. IIRC for 6xx/7xx 3D it was called "programming notes".

          EDIT - sorry, "Driver Notes"... section 6.

          People in glass houses...

          Comment


          • #6
            Originally posted by bridgman View Post
            We include the errata in the programming documentation. IIRC for 6xx/7xx 3D it was called "programming notes".

            EDIT - sorry, "Driver Notes"... section 6.

            People in glass houses...
            Yes because of this articles like this are written.

            Maybe someone should upgrade this erratum list.

            Comment


            • #7
              (scratches head)

              We don't know what the problem is yet. How are we supposed to update the errata ?

              Comment


              • #8
                Originally posted by bridgman View Post
                We include the errata in the programming documentation. IIRC for 6xx/7xx 3D it was called "programming notes".

                EDIT - sorry, "Driver Notes"... section 6.
                Are you saying Jerome Glisse doesn't know how to read? You'd think in 7 months he would've thought to consult that section to find the proper way to deal with this.

                Just so it's clear, I think it's reasonable that something could've been lost or forgotten. We're human, we make mistakes. But with that being the case, let's revisit the docs, find out whatever errata is missing, and publish it.
                Last edited by halfmanhalfamazing; 07-14-2012, 04:17 PM.

                Comment


                • #9
                  No, I'm saying this is a problem that didn't show up in diagnostics or while writing the proprietary driver, so there's no solution/workaround to put in the errata.

                  Q was claiming that there were no errata at all. Different discussion.
                  Last edited by bridgman; 07-14-2012, 04:19 PM.

                  Comment


                  • #10
                    Originally posted by halfmanhalfamazing View Post
                    Are you saying Jerome Glisse doesn't know how to read? You'd think in 7 months he would've thought to consult that section to find the proper way to deal with this.
                    Just so it's clear, I think it's reasonable that something could've been lost or forgotten. We're human, we make mistakes. But with that being the case, let's revisit the docs, find out whatever errata is missing, and publish it.
                    Yes funny in fact the open-source driver is best quality Assurance for your hardware you can get.

                    Comment


                    • #11
                      Originally posted by maldorordiscord View Post
                      Yes funny in fact the open-source driver is best quality Assurance for your hardware you can get.
                      Um... no, but it sure is good QA for the documentation and sample code we write to support open source driver development

                      Comment


                      • #12
                        Originally posted by bridgman View Post
                        No, I'm saying this is a problem that didn't show up in diagnostics or while writing the proprietary driver, so there's no solution/workaround to put in the errata.

                        Q was claiming that there were no errata at all. Different discussion.
                        Ok, that makes sense.

                        Comment


                        • #13
                          Originally posted by maldorordiscord View Post
                          Yes funny in fact the open-source driver is best quality Assurance for your hardware you can get.
                          I'm not the smartest person in the world, but it seems that if Bridgman spent less time responding to flames, and more time coding, your issues would get fixed sooner.

                          Now wouldn't they?

                          Comment


                          • #14
                            Might be worth trying older versions of fglrx and see if they cause the same problem. Another remote possibility is something faulty with a card. Try another card with the same chip/stepping to see if it is reproducible.

                            Comment


                            • #15
                              Wait, so if AMD doesn't know what's wrong there, then how does fglrx manage to function right? There must have been some code in it that manages those cases...

                              Comment

                              Working...
                              X