Announcement

Collapse
No announcement yet.

Google's Pixel 3 Is Using The MSM DRM Driver, More Android Phones Moving To DRM/KMS Code

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

  • Google's Pixel 3 Is Using The MSM DRM Driver, More Android Phones Moving To DRM/KMS Code

    Phoronix: Google's Pixel 3 Is Using The MSM DRM Driver, More Android Phones Moving To DRM/KMS Code

    It turns out Google's recently announced Pixel 3 smartphone is making use of the MSM Direct Rendering Manager driver associated with the Freedreno open-source Qualcomm graphics project. Google is also getting more Android vendors moving over to using DRM/KMS drivers to power their graphics/display...

    http://www.phoronix.com/scan.php?pag...o-MSM-DRM-Plus

  • #2
    Wait a moment, is the Pixel 3 truly running on an open source DRM?
    ## VGA ##
    AMD: X1950XTX, HD3870, HD5870
    Intel: GMA45, HD3000 (Core i5 2500K)

    Comment


    • #3
      This is great news!

      Comment


      • #4
        Originally posted by darkbasic View Post
        Wait a moment, is the Pixel 3 truly running on an open source DRM?
        DRM as in Direct Rendering Manager, not the other useless and controversial thing also called "DRM".

        Comment


        • #5
          This is fantastic news! From my experience with debugging TWRP rendering issues on one of my devices, fbdev is an abomination (at least on Android) with tons of device-specific quirks.

          Comment


          • #6
            Fun fact: the first phone ever with KMS support was Openmoko Neo Freerunner with SMedia Glamo back in 2009.

            Comment


            • #7
              That's an improvement. But they should get rid of Android specific interfaces in their whole graphics stack, not just the kernel, and unify it with regular desktop Linux. That would be a major improvement.

              Comment


              • #8
                Originally posted by bofh80
                Does this impact being able to run (eventually) android apps native or with a wrapper ?
                No. This affects device performance, debugability, and the ability to hopefully run more up to date kernels, at least as far as the graphics drivers are concerned. The situation still isnt good with how many proprietary drivers phones ship with

                Comment


                • #9
                  It would be ideal if Android was brought closer to Linux desktop APIs and libraries. That would mean less work for Google developers too. It is a win-win situation for both us Linux users and Android users.

                  Comment


                  • #10
                    Originally posted by TemplarGR View Post
                    It would be ideal if Android was brought closer to Linux desktop APIs and libraries. That would mean less work for Google developers too. It is a win-win situation for both us Linux users and Android users.
                    And they have to start somewhere. Having everything on a single driver interface enables further unification, so how knows, maybe Android T could be based on Wayland?

                    Comment

                    Working...
                    X