Announcement

Collapse
No announcement yet.

2008 Linux Graphics Survey Results

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

  • #21
    Originally posted by KDesk View Post
    But... KMS needs DRI2, so, the pool was wrong. It should have been DRI2 or KMS (and DRI2) and the other options also.
    My understanding was that KMS needed memory management (GEM/TTM), DRI2 also needed memory management but KMS did not need DRI2. They will probably arrive at more or less the same time, however, since they both become possible as soon as memory management is available, and both are considered really high priority by the developers.

    EDIT - bah, ASCII diagram didn't work ;(
    Last edited by bridgman; 23 December 2008, 01:07 AM.
    Test signature

    Comment


    • #22
      Originally posted by bridgman View Post
      My understanding was that KMS needed memory management (GEM/TTM), DRI2 also needed memory management but KMS did not need DRI2. They will probably arrive at more or less the same time, however, since they both become possible as soon as memory management is available, and both are considered really high priority by the developers.

      EDIT - bah, ASCII diagram didn't work ;(
      Oh, yes, you are complete right! The share the memory manager in common... and not DRI2.

      Comment


      • #23
        Originally posted by Eragon View Post
        How can people keep saying linux is not suited for "normal" users if 56% of it's users describe themselves as "mainstream users"??
        Of the four choices available in the survey, IMHO the closest choice to normal was mainstream. The survey is still available in review fashion which helps see how questions and answers can sometimes skew perception of answers. I was looking to see how the survey handled the question of hardware because I have own or use via work a combination of linux booting computers (ex: macbook pro with nvida, two dell laptops with ati, eeepc, amd tower with nvida). The multiple choice answer to that question came close to capturing my collection but is still skewed (IMHO) because it doesn't show the count per manufacturer.

        Comment


        • #24
          Originally posted by RobbieAB View Post
          Windows has done it for years, as has MacOS. Linux has "innovated" with eye-candy instead...
          That is the very sad truth!

          Comment


          • #25
            Originally posted by deanjo View Post
            That's not my theory at all.
            If that's the case, do you have an appropriate 3rd party licence?



            It's fact that despite best intentions and planning thing don't always go as well as expected. Until actual implementation is actually out there and performing as well as expected it's pure speculation.
            Geez... I was just being silly. No need to drive home an obvious point. I hope you didn't burst a vein coming up with your response.

            Comment


            • #26
              I highly doubt that somebody really needs kms. At least it does not matter for me if switching to a vt takes a few monents or if the default res is already the highest possible. Stability is much more important - also correct rendering and flickerfree videos/games when Vsync is enabled. The rest it nice to have, but not a requirement.

              Comment


              • #27
                Originally posted by Kano View Post
                I highly doubt that somebody really needs kms.
                And you're wrong. KMS is extremely important for suspend and hibernation, which is critical for laptop users. It's a huge boon for display hotplug. It's mandatory for developing alternative graphics stacks without duplicating a metric shitload of driver code.

                KMS is way more interesting to me than DRI2 is. GEM interests me most of all, of course. Without it, neither DRI2 nor KMS could really work.

                Comment


                • #28
                  Ok, I do not own a laptop, so I never use suspend. Hibernation/Suspend to Disk is useless anyway because you would read in worst case more data than you would do with a normal boot when you memory is big and used.

                  Comment


                  • #29
                    I guess the argument for suspend/resume is that it maintains your application state as well ?

                    The other advantage to KMS I see is that it puts all of the state info you need for good power management in one place. Right now the engine state is in drm (unless you're running without 3d) and the display state is in ddx, but you really need both to make on-the-fly power management decisions.
                    Test signature

                    Comment


                    • #30
                      Originally posted by Kano View Post
                      Ok, I do not own a laptop, so I never use suspend. Hibernation/Suspend to Disk is useless anyway because you would read in worst case more data than you would do with a normal boot when you memory is big and used.
                      This is true for hibernation/suspend to disk. But what about suspend to RAM? Most of laptop users use it a lot. And it still is at least 2 times slower than on windows (especially while using fglrx - open source driver suspends and resumes the graphics quicker, but still slower than windows!).

                      Comment

                      Working...
                      X