Gnome 3 devs are stupid enough to remove features before some replacement is implemented. Simplified nautilus and (what's much more important for me!) broken keyboard layout configuration. Well, you still can configure what layouts to use, but you can't choose usual shortcut to switch layout, and you can't configure led to indicate alternative layout. Well, I still can use setxkbmap (setxkbmap -layout "us,ru" -option "grp:caps_toggle,grp_led:scroll"), but that's f***ing ridiculous to remove things that were working here for years and propose nothing for replacement! They broke core functionality (who can work without a keyboard?!), and it makes me sick! Update: more haterays to gnome-devs! Gnome 3 overrides xkbmap settings somewhere, I wonder if there's a way to prevent it... Update-2: you can remove gnome-settings-daemon keyboard plugin as a workaround (sudo rm /usr/lib/gnome-settings-daemon-3.0/libkeyboard.so)
Recently I've got a new laptop with OLED panel only to find out that brightness control for OLED panels is not yet supported in Linux. Archlinux wiki page mentions using gamma ramp for controlling perceived brightness using hackish userspace tools (icc-brightness), so my first thought was to implement a hack for i915 driver to expose backlight interface that actually adjusts gamma ramp. So I went to #dri-devel to ask around whether this idea sounds too crazy and it turned out that there are better ways than using gamma ramp. Basically if you use gamma ramp you essentially reduce dynamic range, i.e. if you have 8 bits per pixel at 50% brightness you would get 7 bit, at 25% - 6 bit and that will result in banding artefacts at low brightness levels. To overcome that issue OLED panels actually have an interface to control brightness. There are at least 2 competing "standards" - VESA and Intel proprietary. First one is already supported by i915 driver while latter is not. Unfo
Recently I spent few evenings for hacking wayland . I like idea of wayland - rendering is done completely on client (in whatever way), compositor (server part) is responsible in rendering buffers from clients on the screen. Issue for me was rendering part of weston (reference compositor for wayland) - it uses GLES for compositing, but I want to try wayland and weston on devices without hw acceleration (pure software rendering), and running software GL on PXA270@312MHz does not sound like a good idea, does it? :) So I asked on #wayland@irc.freenode.org if it possible to implement software renderer, Kristian Høgsberg (khr) responded that in master branch of weston repo there's a nice abstraction of renderer, so it's possible to implement pixman renderer. So I did :) weston with x11-backend and pixman renderer khr and pq from #wayland were very helpful, and described place of renderer in wayland architecture, here're some points renderer just performs rendering of
Comments