Announcement

Collapse
No announcement yet.

First Signs Of Wayland Running On Android

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

  • First Signs Of Wayland Running On Android

    Phoronix: First Signs Of Wayland Running On Android

    A developer for Collabora has been bringing Wayland and the reference Weston compositor to Google's Android mobile Linux platform...

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

  • #2
    "Google has been... ensuring that the Chrome/Chromium web-browser will be well-supported natively on Wayland."

    By completely removing all Wayland support on 2012-04-07?

    Comment


    • #3
      What's the objective of running wayland on something that once ran Android?
      I.e., what you end up with here is....
      hardware --> kernel --> display driver --> wayland --> ??? --> acid trip --> profit
      instead of...
      hardware --> kernel --> display driver --> android

      Note: It is no longer Android once you replace Android with wayland....

      Comment


      • #4
        what a psychedelic test. these guy only want to do hypnosis on me LOL

        Comment


        • #5
          pekka i have a question (since i know you participate here from time to time)


          is this work purely a collabora project or they have been contracted by someone else to do that???

          Comment


          • #6
            Originally posted by Darxus View Post
            "Google has been... ensuring that the Chrome/Chromium web-browser will be well-supported natively on Wayland."

            By completely removing all Wayland support on 2012-04-07?
            OMG why? (stupid character limit)
            ## VGA ##
            AMD: X1950XTX, HD3870, HD5870
            Intel: GMA45, HD3000 (Core i5 2500K)

            Comment


            • #7
              Name complaints

              People MOAN and COMPLAIN about code names for one-shot projects, but HERE we have two projects, Weston and Wayland, which are NOT temporary for releases, but the actual permanent names of the projects.

              If you are familiar with the namesake towns in Eastern Massachusetts, you will understand RIGHT AWAY how STUPID it was to name these Free Technologies for Everyman, after these towns. These towns are the Scourge of Massachusetts, they think that their trees and water and air and sunshine belong to THEMSELVES and no others. They are the ONLY towns in Massachusetts that have declined to take part in the Eastern Massachusetts Bikeway, and so GREAT PAINS have had to be taken to re-route the trail to deal with these SNOOTY RICH PEOPLE who don't want those criminals with their bicycles invading their town.

              The FOOLS were taken in by studies showing that bicycle trails attract crime but NEGLECTED to notice that ABANDONED RAILROAD tracks attract EVEN MORE crime!

              Why not names these technologies after hard working blue collar Massachusetts towns like Townsend or Gardner.

              BEEFY MIRACLE will soon and shortly forgotten but these terrible names will be with us for a long time.

              I must add that in all my years and thousands of miles of bicycling in many states that the ONLY time I have ever had something thrown at me from a moving car was in Weston.
              Last edited by frantaylor; 04-27-2012, 07:04 PM.

              Comment


              • #8
                Originally posted by frantaylor View Post
                People MOAN and COMPLAIN about code names for one-shot projects, but HERE we have two projects, Weston and Wayland, which are NOT temporary for releases, but the actual permanent names of the projects.
                You know nobody in a position to do anything about this is going to read it here, right?

                Comment


                • #9
                  Originally posted by droidhacker View Post
                  What's the objective of running wayland on something that once ran Android?
                  I.e., what you end up with here is....
                  hardware --> kernel --> display driver --> wayland --> ??? --> acid trip --> profit
                  instead of...
                  hardware --> kernel --> display driver --> android

                  Note: It is no longer Android once you replace Android with wayland....
                  It makes it possible to test wayland-apps on android right now? That's useful if we eventually get a more direct wayland path on android (or plain linux on the same hardware), since it means we'll have slightly better-tested software available. It also makes it possible to run wayland apps on top of android, if you should want that (sort of like why you might want an X server in MacOS X).

                  Comment


                  • #10
                    Originally posted by droidhacker View Post
                    Note: It is no longer Android once you replace Android with wayland....
                    That sounds about equivalent to you reading "First Signs Of Wayland Running On Linux" and saying "It's no longer Linux once you replace Linux with wayland."

                    Doesn't make any sense.

                    He didn't replace Android with Wayland. He replaced Android's UI with Wayland, much like Wayland is being made to work in place of X on Linux. And similarly, I'd guess the plan is to make Android's UI work through Wayland as X works through Wayland. Or maybe modify Android to do all its output directly through Wayland.

                    Comment


                    • #11
                      Originally posted by dnebdal View Post
                      It makes it possible to test wayland-apps on android right now? That's useful if we eventually get a more direct wayland path on android (or plain linux on the same hardware), since it means we'll have slightly better-tested software available. It also makes it possible to run wayland apps on top of android, if you should want that (sort of like why you might want an X server in MacOS X).
                      I'm not really sure how it's possible to get a more direct than Weston drawing directly to the framebuffer as it does now.

                      Comment


                      • #12
                        Originally posted by droidhacker View Post
                        What's the objective of running wayland on something that once ran Android?
                        I.e., what you end up with here is....
                        hardware --> kernel --> display driver --> wayland --> ??? --> acid trip --> profit
                        instead of...
                        hardware --> kernel --> display driver --> android

                        Note: It is no longer Android once you replace Android with wayland....
                        That's actually a fairly accurate description, replacing Android with Wayland, because pretty much every Android system service and interface directly or (most often) indirectly depends on SurfaceFlinger. Even the power button, whose action is to show a dialog for shutdown/something/cancel/whatever, and it cannot show anything without SurfaceFlinger, so it just doesn't work anymore.

                        The objective is to offer an alternative for Android, and take advantage of the huge amount of devices and drivers already written for them. In the future we can start getting familiar programs on those devices. That is what open source is.

                        89c51, it has been Collabora's own project.

                        Like daniels said, there is no more direct path that what I did: Weston runs directly on top of the framebuffer. It is taking SurfaceFlinger's place.

                        Running existing Android stuff on top of Wayland is a whole another story, and I personally do not have plans for it. It would be a huge project about rewriting several Android components, and what would be even more difficult, interfacing to existing Android system services in proper ways.

                        Comment


                        • #13
                          Originally posted by pq__ View Post
                          89c51, it has been Collabora's own project.

                          thanks for the answer

                          Comment


                          • #14
                            Originally posted by Darxus View Post
                            That sounds about equivalent to you reading "First Signs Of Wayland Running On Linux" and saying "It's no longer Linux once you replace Linux with wayland."

                            Doesn't make any sense.

                            He didn't replace Android with Wayland. He replaced Android's UI with Wayland, much like Wayland is being made to work in place of X on Linux. And similarly, I'd guess the plan is to make Android's UI work through Wayland as X works through Wayland. Or maybe modify Android to do all its output directly through Wayland.
                            If you understood Android, you would understand why you are incorrect. Basically, there is a kernel and a few basic utilities, everything above that is Android. As pq__ stated, because of the dependencies, once you change out Android's "UI", all that's left is Linux and a few utilities. Android is gone.

                            It is still, however, Linux....

                            Comment


                            • #15
                              Originally posted by droidhacker View Post
                              If you understood Android, you would understand why you are incorrect. Basically, there is a kernel and a few basic utilities, everything above that is Android. As pq__ stated, because of the dependencies, once you change out Android's "UI", all that's left is Linux and a few utilities. Android is gone.

                              It is still, however, Linux....
                              From a user perspective, Android is gone, yes. But there is still some serious infrastructure left: the build tools and toolchains, installing and debugging tools (adb etc.), HALs, bootloaders(?), and hardware "support" that is not in upstream Linux and might never be. In my opinion, calling that "Linux and a few utilities" is an understatement. But that is a developer's point of view.

                              Comment

                              Working...
                              X