aura+wayland shoud be an excellent improvement.
Announcement
Collapse
No announcement yet.
Google Replacing GTK2 With Aura In Chrome 35
Collapse
X
-
Originally posted by arekm View PostSame here. Likely needs patch like:
Code:--- chromium-browser/content/common/gpu/media/gpu_video_decode_accelerator.cc~ 2014-02-20 21:28:24.000000000 +0100 +++ chromium-browser/content/common/gpu/media/gpu_video_decode_accelerator.cc 2014-03-12 16:52:52.265999592 +0100 @@ -278,7 +278,7 @@ weak_factory_for_io_.GetWeakPtr(), make_context_current_, io_message_loop_)); -#elif defined(OS_CHROMEOS) && defined(ARCH_CPU_X86_FAMILY) && defined(USE_X11) +#elif defined(OS_LINUX) && defined(ARCH_CPU_X86_FAMILY) && defined(USE_X11) gfx::GLContextGLX* glx_context = static_cast<gfx::GLContextGLX*>(stub_->decoder()->GetGLContext()); GLXContext glx_context_handle =
Comment
-
File a bug asking them to enable it on Linux when the kernel, libva, and other dependencies are up-to-date. If lots of bugs are opened about the deficiencies on Linux, they might reconsider whether crippling it by disabling hardware acceleration is actually reducing the number of bug reports.
Comment
-
-
Originally posted by abral View PostWell, this isn't true. They've used the webkit browser engine, and in a browser the browser engine is definitely the most difficult part to write (indeed no one writes new browser engines, even Apple didn't do their own thing and used KHTML. Only recently Mozilla has started Servo, but it's still in its early stages). So you can't say they've written it from scrath.
Regardless, Google is only replacing GTK in the browser part of their browser, not the html engine, which doesn't directly connect with any toolkit. So just looking at the shell/UI alone, that is 100% written by google.
Comment
-
Originally posted by pandev92 View Postdoesn't work for me, opensource amd drivers, vdpau activated, but flash only " accelerated video rendering, software video decoding"
- Mesa compiled with VDPAU support. That means: if you use Ubuntu, you need at least a recompile.
- VDPAU libraries.
HIGHLY RECOMMENDED:
- Mesa 10.1. You need GLSL 1.50 for some HW decoding paths.
- vdpauinfo. Check if your VDPAU setup is working.
- The following in your ~/.bashrc file
Code:export LIBVA_DRIVER_NAME=vdpau export VDPAU_DRIVER=r600
Comment
-
-
Originally posted by Alejandro Nova View PostThe requirement set is strict. You need:
- Mesa compiled with VDPAU support. That means: if you use Ubuntu, you need at least a recompile.
- VDPAU libraries.
HIGHLY RECOMMENDED:
- Mesa 10.1. You need GLSL 1.50 for some HW decoding paths.
- vdpauinfo. Check if your VDPAU setup is working.
- The following in your ~/.bashrc file
Code:export LIBVA_DRIVER_NAME=vdpau export VDPAU_DRIVER=r600
I use xorg edgers ppa with vdpau activated, the latest google chrome unstable from google ppa, and it doesn't work.
Comment
-
Well, I definitely noticed how the initial website rendering after loading is a lot smoother for at least some websites, like e.g. google plus or youtube.
edit: but font rendering is looking very different. Not sure if it's better or worse yet. At least they don't have colored anti aliasing by default! Yay!
FYI, there are also builds for chromium from google, not just for chrome. Shamelessly copied from an AUR package:
Code:wget http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux_x64/$(curl -s "http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux_x64/LAST_CHANGE")/chrome-linux.zip
The difference between chromium and chrome: If there is tracking or phone-home code in chromium enabled, it's a bug that's getting fixed. In chrome it's a feature.
Comment
Comment