Announcement

Collapse
No announcement yet.

OpenChrome Maintainer Making Some Progress On VIA DRM Driver

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

  • OpenChrome Maintainer Making Some Progress On VIA DRM Driver

    Phoronix: OpenChrome Maintainer Making Some Progress On VIA DRM Driver

    Independent developer Kevin Brace took over maintaining the OpenChrome DDX driver earlier this year to improve the open-source VIA Linux graphics support while over the summer he's slowly been getting up to speed on development of the OpenChrome DRM driver...

    http://www.phoronix.com/scan.php?pag...-Some-Progress

  • #2
    what vis system he use?

    Comment


    • #3
      Originally posted by Azrael5 View Post
      what vis system he use?
      he covers it all in his long email.
      Michael Larabel
      http://www.michaellarabel.com/

      Comment


      • #4
        why don't make more efficient pt880 890 and vtxxx chipset drivers!?

        Comment


        • #5
          Because these chipsets are utter, buggy crap from the past, launched more than 10 years ago, put to rest by their defunct manufacturer more than 5 years ago.

          Comment


          • #6
            Originally posted by Azrael5 View Post
            why don't make more efficient pt880 890 and vtxxx chipset drivers!?
            Because most of the issues of those chipsets are in hardware, crappy board design, or in BIOS firmware (or a combination of these), not in drivers. And because what Hibbelharry said above too, they are also obsolete crap, the solution to all issues with obsolete crap hardware is replacing it with non-obsolete non-crap hardware.

            Comment


            • #7
              Originally posted by starshipeleven View Post
              Because most of the issues of those chipsets are in hardware, crappy board design, or in BIOS firmware (or a combination of these), not in drivers. And because what Hibbelharry said above too, they are also obsolete crap, the solution to all issues with obsolete crap hardware is replacing it with non-obsolete non-crap hardware.
              I assumed this developer was working on legacy system. However I know the mentioned chipsets are rather obsolete anyway linux operating systems have not so much problem with motherboards provided by them, also assumed their limitations. It is always possible to improve.

              Comment


              • #8
                Originally posted by Azrael5 View Post
                I assumed this developer was working on legacy system.
                He is working on GPUs, not on chipsets. The chipset drivers are as good as they can get since a long time.

                It is always possible to improve.
                No it is not, and even when it is possible it may be VERY impractical.
                Fixing hardware bugs is not possible, period. The chip was printed like that.
                Fixing board design issues is theoretically possible IF you have the board schematics and an electrical engineer to trace the root cause so you can work around it in firmware (if possible).
                Fixing firmware issues is theoretically possible IF you have the board schematics, the source of the blobs produced by VIA that initialize the hardware, the source of other blobs that make up the BIOS that come from BIOS vendor, and again some low-level developers (usually engineers) to trace the root causes and try to fix them.

                Really, stuff becomes obsolete for a reason. Way too expensive to fix or improve for anyone to really try.

                Comment


                • #9
                  Originally posted by starshipeleven View Post
                  He is working on GPUs, not on chipsets. The chipset drivers are as good as they can get since a long time.

                  No it is not, and even when it is possible it may be VERY impractical.
                  Fixing hardware bugs is not possible, period. The chip was printed like that.
                  Fixing board design issues is theoretically possible IF you have the board schematics and an electrical engineer to trace the root cause so you can work around it in firmware (if possible).
                  Fixing firmware issues is theoretically possible IF you have the board schematics, the source of the blobs produced by VIA that initialize the hardware, the source of other blobs that make up the BIOS that come from BIOS vendor, and again some low-level developers (usually engineers) to trace the root causes and try to fix them.

                  Really, stuff becomes obsolete for a reason. Way too expensive to fix or improve for anyone to really try.
                  it could be possible to create a bios which program itself maching the hardware used reading their firmware specifications?

                  Comment


                  • #10
                    Originally posted by Azrael5 View Post
                    it could be possible to create a bios which program itself maching the hardware used reading their firmware specifications?
                    I'm not sure I understand what you mean for "bios which programs itself".
                    Conventional software cannot do much more than assembling pre-made blocks (binaries or code) following a rigid logic encoded by someone, and this does not solve the problem as someone still had to write the logic, prepare the pre-made blocks and make sure that everything worked.

                    If you mean a software that can figure out by itself how to do things by reading a manual and by troubleshooting hardware that does not work exactly as the spec, it's a software that knows how to think, at least in his specific field, so a specialist artificial intelligence for the very least.

                    Not the "100% people" AIs in movies, mind me, that would still be a program that has no idea of anything outside of its field, like Google's Picasa image tagging algorithms.

                    Comment

                    Working...
                    X