Announcement

Collapse
No announcement yet.

How Google's Android Runtime On Chrome OS Uses Wayland, DRM

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

  • How Google's Android Runtime On Chrome OS Uses Wayland, DRM

    Phoronix: How Google's Android Runtime On Chrome OS Uses Wayland, DRM

    Google developer David Reveman presented at this morning's XDC2016 conference in Finland about the Android Runtime for Chrome making use of Wayland (ARC++) and how the rest of its graphics stack looks for running Android programs on Chrome OS...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Very cool to see Google using the bleeding edge Linux graphic stack to run Android in consumer products before it's even used by classic distributions.

    That's promising for the future of Wayland and the open Linux graphic stack.

    Comment


    • #3
      Personally, I'm happy to see the mastermind behind Compiz at the helm.

      Comment


      • #4
        Originally posted by wagaf View Post
        Very cool to see Google using the bleeding edge Linux graphic stack to run Android in consumer products before it's even used by classic distributions.

        That's promising for the future of Wayland and the open Linux graphic stack.
        I find myself with mixed feelings about Google. On the downside:
        - Their revenue model is built on advertising, which means it is in their financial interest to know everything possible about their users.
        - They support digital rights management in their products - Android, Chrome, Chrome OS.
        - They support open source often but proprietary software when it suits them. They could insist that any device permitted to use the Android logo release all device driver firmware as open source, and they don't. Their search technology and flagship Android applications are proprietary.
        - The support life cycle for Android products is very short, and Google could push manufacturers to make it longer but does not.

        On the upside:
        - They don't wield their patents like a weapon against innovators.
        - They implement open standards, and the competition has been forced into complying with those standards to keep up.
        - They do release a lot of code as open source, and I really think Microsoft only made .NET open source and Apple made Swift open source because of Google.
        - Even when they don't release a product as open source, they share the ideas and whitepapers. BigTable. Borg. etc... etc...

        In the middle:
        - If Google didn't implement digital rights management, they never would have gotten the rights to all of the media they make available to users. If you want to stream Disney movies, your choices are: "Digital Rights Management" or "No Deal".
        - If Google pushed hardware manufacturers harder on device drivers or support cycles, those companies would not have offered Android. So Android would have never taken off. The choice was "support proprietary drivers and planned obsolescence" or "be insignificant".

        Comment


        • #5
          Die Mir, die.
          ## VGA ##
          AMD: X1950XTX, HD3870, HD5870
          Intel: GMA45, HD3000 (Core i5 2500K)

          Comment


          • #6
            Man fuck your digital rights management!

            Comment


            • #7
              David Reveman's presentation starts at about 2:11:00 in the following YouTube video:

              Welcome to the X.org Developer Conference 2016, day 1, slides are located at https://www.x.org/wiki/Events/XDC2016/Program/ and here are the different talks:...

              Comment


              • #8
                Originally posted by uid313 View Post
                Man fuck your digital rights management!
                If you want to do business with Disney, Universal Studios, or Sony, you need the DRM. So Google, as big as they are, had two choices:

                1. No Disney, Warner Brothers, Universal, Sony, etc... content available on Android.
                2. DRM.

                Comment


                • #9
                  Originally posted by uid313 View Post
                  Man fuck your digital rights management!
                  To be clear, DRM here means Direct Rendering Manager, nothing to do with right management.

                  Comment


                  • #10
                    From the article:
                    ARC++ makes use of DRM with render-nodes for allowing the Android program to access the GPU and buffers are shared via DMA-BUF.
                    Also from the article:
                    Google developers are also looking at working on Wayland extensions around explicit synchronization and protect buffers. The protected buffers support on Wayland is for digital rights management support.
                    Originally posted by Michael_S View Post
                    If you want to do business with Disney, Universal Studios, or Sony, you need the DRM. So Google, as big as they are, had two choices:

                    1. No Disney, Warner Brothers, Universal, Sony, etc... content available on Android.
                    2. DRM.
                    For the sake of clarification, I note that the abbreviation DRM as used in this article is short for Direct Rendering Manager.

                    But yes, I agree that, for better or worse, there is no escaping the need for digital rights management (the other DRM) support.

                    Comment

                    Working...
                    X