Announcement

Collapse
No announcement yet.

Google Chrome Adds VA-API Video Acceleration On Wayland

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

  • #21
    Originally posted by jonkoops View Post
    Is there any news on when the Chrome team is thinking of enabling Ozone by default? It's kind of a bummer Chrome still needs to use XWayland by default in Wayland environments.
    Last I looked there were still a couple of handfuls of blockers for Chrome Wayland (although one/two looked to just be documentation related).

    And other XWayland apps such as VSCode with an updated Electron may also enable Wayland by default RSN.

    This may finally be the year when Linux desktop environment and apps will be primarily Wayland. There has been a lot of work by a lot of developers to get to this point. It is all finally coming together.

    Comment


    • #22
      Ah, this finally explains it. I am a Firefox user but wanted to try Vivaldi, if nothing else as a backup. However I spent days trying all the different methods posted online of getting VA-API working and nothing happened. So, it was simply because it's not supported on Wayland so no number of flags, switches or animal sacrifices will do anything until that's fixed.

      Comment


      • #23
        Originally posted by juxuanu View Post
        Chromium catching up with Firefox.
        Just like wayland catching up with X after 15 years. Looooooong way to go

        Comment


        • #24
          Awesome! For which release is it set?
          Last edited by MorrisS.; 06 January 2024, 02:05 PM.

          Comment


          • #25
            Originally posted by jonkoops View Post
            Is there any news on when the Chrome team is thinking of enabling Ozone by default? It's kind of a bummer Chrome still needs to use XWayland by default in Wayland environments.
            There is an option on flag page in the browser where you can enable the option AUTO. So the browser switches to the X11 or Wayland stack automatically. SPhtzRn.png
            Last edited by MorrisS.; 06 January 2024, 02:05 PM.

            Comment


            • #26
              Originally posted by avis View Post
              ChromeOS doesn't use either X11 or Wayland.

              That wrong these days. ChromeOS has its own Wayland compositor called exo/exosphere.

              The reason why waydroid works so well is ARC on ChromeOS for running Android applications has Android applications on chromeos running on top of Wayland protocol.

              Yes lacros is changing the web browser under ChromeOS to sit on top of Wayland as well.

              Avis in a lot of ways Chromeos is slowly migrating to more and more Wayland Protocol based solution from their own internal custom protocol. So ChromeOS is increasing in Wayland usage. Migrating from one protocol to another is not exactly fast.



              Yes the ARC build of android for ChromeOS is part of what is called the Android platform. Not all forms of Android is the bare metal forms avis.

              This does bring the interesting question of course will google ever decide do in surfaceflinger protocol and go to a wayland compositor instead. This is a question because they are doing in the chromeos unique protocol.

              Comment


              • #27
                Originally posted by avis View Post
                Android can hardly be called Linux at all. A highly patched Linux kernel and completely different user space.
                Android kernel is Linux, no matter how much patched it is. Even RHEL kernel is heavily patched, but it still is Linux.
                Regarding userspace, it's, well, userspace, that is a completely separate thing from the kernel.


                Comment


                • #28
                  Originally posted by Hibbelharry View Post

                  You're mentioning Clang. Did you test with gcc and does that fix the problem?
                  While the website rendering was fine with a GCC-compiled Mesa, I've seen the crashes that took down the whole system with both GCC and Clang.

                  Comment


                  • #29
                    Originally posted by juxuanu View Post
                    Chromium catching up with Firefox.
                    Sadly, Mozilla (Firefox) seems to be circling the drain. It has little remaining relevancy in the market as a whole, even as it shows it still has good developers on some teams. Removing features, paying your CEO nearly $7M/yr, all the while operating with over 85% of your total revenue depending on one company (Google, for search for advertising) it is difficult to be considered entirely healthy and truly independent. While I would like to see Mozilla become relevant again, it likely missed too many boats.

                    Comment


                    • #30

                      Originally posted by Leinad View Post

                      ChromeOS uses Wayland since version 115. Android Linux kernel diff to vanilla is pretty low nowadays.
                      ​​

                      see below

                      Originally posted by avis View Post

                      And none of them is Linux/GNU.

                      Android can hardly be called Linux at all. A highly patched Linux kernel and completely different user space.

                      ChromeOS doesn't use either X11 or Wayland.
                      Android works perfectly fine on the upstream kernel, yes the userland bits like the compositor and permissions handling are different, but you can still just run linux apps just fine on android, and hell x11 apps work great when using termux-x11.​ The actual differences with the android kernel phones use and mainline are mostly some bits and bobs regarding the proprietary modules. Android will run on just about most distro's kernels now out of box, there are some like PopOS that don't enable binder, but distros like fedora and arch's zen kernel are 100% compatible with android, this is actually how waydroid works, since waydroid is just android in a container with some patches to sound, input, and display parts of android's stack to get it "feeling native".

                      but you can install and run apps perfectly fine on android without a chroot/proot, with termux you get native xfce, firefox, and many more gui packages, and with a chroot you can get even more since you have accsess to 90% of that distros stuff

                      Comment

                      Working...
                      X