RADV's ACO Compiler Back-End Now Supported For Older AMD "Sea Islands" GPUs

The Valve-backed "ACO" compiler back-end for the open-source Radeon "RADV" Vulkan driver has added support now for AMD GCN 1.1 "Sea Islands" graphics cards. Sea Islands includes the Radeon Rx 200 series with the R7 260/260X/290/295 series and these 2nd Gen GCN GPUs also ended up in the Radeon HD 7790, Radeon HD 8770, Radeon R7 360, Radeon R9 390/390X, and Radeon RX 455. Up to now the ACO compiler back-end has only supported GCN1.2/GFX8 and newer but with the latest Mesa 20.0-devel code as of today in Mesa Git there is now ACO support for GCN 1.1 Sea Islands.

Wayland's Weston 8.0 Reaches Alpha With EGL Partial Updates, Headless OpenGL

Weston 8.0 is another significant update for this Wayland reference compositor in it offers EGL_KHR_partial_update support to reduce GPU vRAM usage on supported drivers/GPUs thanks to handling partial screen updates, support for building the DRM back-end without Mesa's GBM, greater hardware planes usage, the Weston headless back-end now supports OpenGL, a direct display extension, HDCP support in the DRM back-end, and various other improvements / features.

weston 7.0.91

This is the alpha release for weston 8.0. Here is a highlight of the
main new features:

- DRM hardware planes should be used more effectively
- Headless backend now supports OpenGL
- DRM backend can now be built without GBM
- EGL_KHR_partial_update is now used when available, reducing memory
  bandwidth usage on some GPUs
- Logging framework improvements
- Documentation for weston can now be built

A lot of fixes have been merged too. Thanks to all contributors!

Full commit history below.

Adam Jackson (5):
      simple-dmabuf-egl: Allow QueryDmaBufModifiers to report no modifiers
      gl-renderer: Fix possible memory leak when no dmabuf modifers are supported
      libweston: Fix integer underflow in weston_layer_mask_is_infinite
      image-loader: Fix undefined left shift in premultiply_data
      tests: Fix undefined left shift in internal-screenshot-test

Ankit Nautiyal (6):
      backend-drm: Add support for content-protection
      libweston: Add functions to modify disable_planes counter for an output
      libweston: Add function to schedule idle task for updating surface protection
      libweston: Notify the client, when output recording is started/stopped
      man: Declare drm-backend support for HDCP
      backend-drm: Check for HDCP Content Type property before setting

Daniel Stone (8):
      renderer-gl: Assert function presence matches extensions
      remoting: Use DRM FourCC formats instead of GBM formats
      Revert "backend-drm: Teach drm_property_info_populate() to retrieve range values"
      config-parser: Export get_full_path and destroy
      backend-drm: Use aspect-ratio bit definitions from libdrm
      config-parser: Make get_bool be bool
      tests/config-parser: Remove useless duplicate test
      option-parser: Make bools boolean

Drew DeVault (1):
      simple-dmabuf-egl: update to xdg-shell stable

Eero Tamminen (1):
      Add include for missing symbols

Emmanuel Gil Peyrot (1):
      shared: Use memfd_create() when available

Harish Krupo (3):
      gl-renderer: Censor protected views when output is recorded
      clients/window: Add viewport destination support
      desktop-shell: Set 1x1 buffers for solid-color backgrounds

Jeffy Chen (2):
      clients: Drop corresponding touch points when destroying windows
      clients: Add more sanity checks to catch destroyed window

Leandro Ribeiro (11):
      build: bump libdrm requirement to newer version (2.4.83)
      backend-drm: remove unecessary ifdef checks
      backend-drm: remove unnecessary ifdefs
      move frame_signal emission to weston_output_repaint()
      screenshooter: stop using frame_signal void *data parameter to get weston_output
      tests: stop using frame_signal 'void *data' argument to get weston_output
      renderer: change frame_signal emission to pass previous_damage as data argument
      screenshooter: get previous_damage from data argument instead of weston_output
      screen-share: get previous_damage from data argument instead of weston_output
      Revert "move frame_signal emission to weston_output_repaint()"
      libweston: remove previous_damage from struct weston_output

Link Mauve (1):
      xwayland: Remove unused variable

Loïc Yhuel (1):
      libweston: fix possible crash after a view is removed the layer

Marius Vlad (53):
      weston-log: s/scope/sub, leftover from the logging framework
      libweston: Fix rename of weston_compositor_destroy() reference
      weston-log: 'new_subscriber' is actually 'new_subscription'
      weston-log: Add 'destroy_subscription' callback for the subscription
      weston-log-internal: Allow to hang-off data over the subscription
      weston-log: Add a subscription iterator
      libweston: Clean-up timeline to make room for a new approach
      libweston: Introduce timeline subscription and timeline subscription object
      libweston: Create the 'timeline' scope
      libweston: Convert timeline points to use the timeline scope
      libweston: Notify timeline of object modification
      libweston: Remove timeline-object and clean-up
      doc/sphinx: Add some documentation about timeline points
      compositor: Allow protocol to be displayed when asked for, even if we're not supplying debug argument
      libweston: Init weston_output's 'destroy_signal' before timeline has a chance to emit a
      compositor: Pass the entire string in one-shot when writting logger data
      weston-log: Avoid prefix-matching the scope name when checking for a
      backend-drm: Teach drm_property_info_populate() to retrieve range values
      backend-drm: Teach drm_property_info_populate() to retrieve range values
      backend-drm: Add zpos DRM-property
      backend-drm: Add a helper to display plane type as a 'string'
      backend-drm: Hard-code zpos values if HW doesn't exposes them
      libweston: Add a new helper weston_view_has_valid_buffer
      libweston: Add a new helper to check if the view spawns the entire
      backend-drm: Construct a zpos candidate list of planes
      backend-drm: Place pixel format checks for the overlay plane in its own
      backend-drm: Place pixel format checks for the cursor plane in its own
      backend-drm: Check pixel format before constructing the zpos candidate list
      backend-drm: Allow for views to reach overlays/underlays planes
      backend-drm: Pass the plane to prepare_overlay_view
      backend-drm: Pass the drm_fb to each prepare_overlay/scanout_view functions
      backend-drm: Move plane's availability in drm_output_try_view_on_plane()
      backend-drm: Print whenever a view will reach the renderer region
      backend-drm: Print whenever a view could not placed on the primary due to
      compositor: Fix some warning when passing debugoptimized to meson
      protocol: Add weston-direct-display extension
      libweston: Add weston-direct-display server side implementation
      libweston: Add the ability to determine if a dmabuf is scanout-capable
      backend-drm: Add dmabuf scan-out check for DRM-backend
      renderer-gl: Avoid retrieving the EGL image it direct_display flag was set
      renderer-gl: Display a solid shader color when direct-display is in use
      clients/simple-dmabuf-egl: Make use of direct-display
      clients/simple-dmabuf-drm: Make use of direct-display
      backend-drm: Assign the primary plane the lowest zpos value
      backend-drm: Skip testing plane state if plane is not enabled
      backend-drm: Turn zpos duplicate check into an hard assert
      backend-drm: Further checks to skip plane assignment to HW planes
      weston-log-flight-rec: Add a global variable to access the ring buffer
      weston-log-flight-rec: Don't allow more than one flight recorder to be
      weston-log-flight-rec: Fix useless comparison when displaying the
      doc/scripts/gdb: Added gdb script to dump contents of the flight recorder
      clients/fullscreen: Refuse to resize the surface size when fullscreen'ed
      gitlab-ci: Update ci-templates to latest SHA commit

Miguel A. Vico (2):
      desktop-shell: Avoid NULL output dereference when getting surface label
      compositor: Do not trigger invalid destructors when hotunplugging

Nicholas Niro (2):
      backend-drm: Fix for gbm modifiers when they are not available.
      backend-drm: Added support for legacy fd_import

Olivier Fourdan (1):
      xwm: Use Xwayland allow commits for repaint

Pekka Paalanen (73):
      backend-headless: fix comment on use_pixman
      backend-headless: refactor into headless_output_enable_pixman
      backend-headless: refactor into headless_output_disable_pixman
      backend-headless: make renderer type an enum
      clients: fix len-string formatting
      gl_renderer: remove unused NO_EGL_PLATFORM
      gl-renderer: fix typo native_window to native_display
      gl-renderer: remove platform_attribs
      gl-renderer: remove gl_renderer_display
      gl-renderer: remove gl_renderer_output_surface
      gl-renderer: remove print_egl_error_state
      backend-drm: use format db for fallback too
      gl-renderer: move into egl-glue.c
      gl_renderer: introduce gl_renderer_get_egl_config()
      gl-renderer: use gl_renderer_get_egl_config() for display_create
      gl-renderer: do not even pick a config with configless_context
      pixel-formats: add RGBA bits and type fields
      gl-renderer: use pixel_format_info internally for EGL
      gl-renderer: fuzzy EGLConfig matching for non-GBM
      backend-wayland: use DRM formats for EGLConfig
      backend-x11: use DRM formats for EGLConfig
      gl-renderer: remove EGLConfig attributes from API
      gl-renderer: configs for pbuffers too
      gl-renderer: pbuffer config for non-surfaceless
      gl-renderer: prefer the base EGLConfig
      gl-renderer: improve get_egl_config errors
      gl-renderer: print detailed EGLConfig list
      gl-renderer: use EGLConfig printer for window outputs
      build: shells do not need matrix.c
      build: use dependency for matrix.c
      xwm: dnd does not need cairo-util.h
      Unify the include style of shared/ headers
      build: simplify include_directories
      xwm: no need for compositor/weston.h
      gl-renderer: display_create needs surface type
      gl-renderer: document display_create
      gl-renderer: document output_window_create
      gl-renderer: add EGL surfaceless platform support
      noop-renderer: zero-initialize struct
      headless, gl-renderer: support pbuffer outputs
      compositor: add use-gl option to headless
      gitlab-ci: fix pages
      build: separate deps for int and ext libweston users
      build: link libm explicitly
      build: link libdl explicitly to DRM backend
      backend-x11: need libdrm headers in build
      build: reduce sub-dependencies of libweston
      compositor: turn weston main() into a lib
      cms-colord: work around unresolved symbols
      backend-rdp: work around unresolved symbols
      Link Weston plugins to libexec-weston.so
      tests: surface-screenshot needs libshared
      build: do not allow unresolved symbols
      libweston: drop a misleading dmabuf comment
      tests: remove static data from viewporter
      tests: remove static data from ivi-layout-test-plugin
      tests: remove static data from ivi-shell-app-test
      tests: remove static data from ivi-layout-test-client
      tests: remove static data from presentation
      tests: fix test-shell init error path
      ivi-shell: fix init error path
      colord: remove destroy listener on clean-up
      Use weston_compositor_add_destroy_listener_once() in plugins
      libweston: allow double-loading modules
      compositor: allow double-loading modules
      tests: write image to current directory by default
      tests/subsurface-shot: hardcode reference image names
      tests: replace fprintf() with testlog()
      tests/xwayland: do not call exit(SUCCESS)
      tests: rename struct weston_test to weston_test_entry
      tests/ivi: rename test_section
      tests: drop FAIL_TEST
      libweston: do not include weston.h

Sebastian Wick (7):
      shared: add read-only anonymous file abstraction
      CI: build wayland from source
      input: bump wl_seat version to 6
      clients/window: bump wl_seat version to 6
      input: bump wl_seat version to 7
      clients/window: bump wl_seat version to 7
      input: use ro_anonymous_file to minimize duplication of keymap files

Simon Ser (4):
      build: reopen master for regular development
      clients: drop simple-dmabuf-drm
      clients: remove leftover from simple-dmabuf-drm
      build: bump to version 7.0.91 for the alpha release

Stefan Agner (10):
      backend-rdp: don't use shadow buffer for the RDP backend
      backend-headless: fix build issue without gl-renderer
      clients: avoid build error without gl-renderer
      gitlab-ci: add build configuration without gl-renderer
      backend-drm: use DRM_ constants everywhere
      remoting: make sure GL renderer is enabled
      backend-drm: separate out DRM virtual support
      backend-drm: make GBM optional
      weston-launch: show when a signal is sent to a child
      weston-launch: use exec to ensure signal delivery

Veeresh Kadasani (1):
      simple-dmabuf-egl: make application generic

Vivek Kasireddy (2):
      gl-renderer: Replace EGL_*_WL macros with locally defined enums
      gl-renderer: Add support for XYUV format (v2)

sichem (1):
      libweston: Bring back 'weston_output_move'

git tag: 7.0.91

Mesa 20.0 Now Includes Intel's Gallium3D Driver To Build By Default

As part of the ongoing effort for Intel's plans to use their new Gallium3D OpenGL Linux driver by default on next quarter's Mesa 20.0 for Broadwell "Gen8" graphics and newer, another step in that direction was achieved on Friday. Intel's "Iris" Gallium3D driver is still making good progress in its goal for Mesa 20.0 to switch the default "i965" classic driver to Intel Gallium3D for Broadwell and newer hardware. Earlier this week was adding a build-time option to change the Intel OpenGL driver default so those building from source or distribution vendors can change the default on their own with ease.

GRUB Now Supports Btrfs 3/4-Copy RAID1 Profiles (RAID1C3 / RAID1C4 On Linux 5.5+)

When it comes to the storage/file-system changes with the in-development Linux 5.5 kernel one of the most prominent end-user-facing changes is more robust RAID1 for Btrfs with the ability to have three or four copies of the data rather than just two copies, should data safety be of utmost importance and concerned over the possibility of two disks in an array failing. The Btrfs "RAID1C3" mode was merged last week for this three/four-copy RAID1 while now the GRUB boot-loader has adapted support for these new profiles in order to be able to boot to said arrays.

Linux 5.5 Adds NFS Client Support For Cross-Device Offloaded Copies (Server To Server)

With NFSv4.2 is the server-side copy (SSC) functionality with the Linux 5.5 kernel's NFS client-side support for that support in allowing "inter" copy offloads between different NFS servers. This support allows for server-to-server efficient file copies with NFSv4.2 SSC rather than first having to copy to the client system. The NFS client changes also introduce new RDMA tracepoints for debugging congestion control and various other fixes.

Linux 5.5 KVM Adds POWER Support For Secure Guests/VMs

IBM's work from over a year ago in working towards secure virtual machines on POWER hardware is finally coming to fruition with Linux 5.5 due out early next year. After those original Secure Virtual Machine POWER9 patches were posted last year, the ultravisor / secure bits landed in Linux 5.4 in preparing the foundation. As explained in that earlier article, "The Ultravisor / SVM support is part of IBM's approach for protected computing that is akin to the approaches of Intel SGX and AMD Secure Encrypted Virtualization (SEV). IBM's Ultravisor code runs with higher privileges than the virtualization hypervisor and in turn the virtual machines rely upon IBM Protected Execution for verifying the behavior of the hypervisor/ultravisor."

Install GNU Jami on Ubuntu and Trisquel

Getting Started with NVIDIA Jetson Nano Devkit: Inference using Images, RTSP Video Stream

Kali Linux for android without rooting your device

5 Ways to Crop Videos in Linux

How to Install MongoDB on Debian 10 Linux

How To Git Reset to HEAD

How to install elementary OS 5.1

linux debian (and others) – how to manually install replace firefox-esr 68.2 with latest version 71

Building an OpenShift LDAP URL from FreeIPA

Slow Shutdown – A stop job is running for Snappy Daemon

Minishift on Linux with VirtualBox

Debian init systems GR - voting guide

If you don't know what's going on, you may wish to read my summary and briefing blog post from a few weeks ago. There are 7 options on the ballot, plus Further Discussion (FD). With this posting I'm trying to help voting Debian Members (Debian Developers) cast their votes. I am going to be neutral about the technical merits of systemd. My advice does not depend on your opinion about that. So my advice here is addressed to people who like systemd and want to keep running it, and developing with it, as well as, of course, people who prefer not to use systemd. I'm even addressing readers who think systemd has useful features which they would like Debian packages to be able to use. However, I am going to be opinionated about one key question: My baseline is that Debian must welcome code contributions to support running without systemd, just as it welcomes code contributions for other non-default setups. If you agree with that principle, then this posting is for you. Unfortunately this principle is controversial. Several of the options on the current GR mean rejecting contributions of non-systemd support. So in that sense I am not neutral.

Charles Plessy: I voted

Nevertheless, I am crushed under the number of options. Their texts are long, sometimes very similar, and do not separate clearly the normative from the preambles. Like in a parody of the dysfunctions of modern democracies, I ended up considering only the proposals written or seconded by people with whom I feel in phase. I have not voted for the others, which ranks them equally under « further discussion ».

Update to packaging the Jekyll import tool

For moving my personal blog away from blogger I’ve put a lot of work into packaging and/or updating (the most common) Jekyll plugins for Debian. To ease the work further I began to package the Jekyll importers. But they need some (yet) unpackaged gems. So I’ve created an issue to track the progress and put my work on this package on hold. Yesterday @utkarsh2102-guest contacted me and asked me for more details. So I’ve spent the last hours to track down what actually needs to be done. And the news are a lot better than expected.

When terms and policy turn users away

When asked to accept terms of use and privacy policies that state it will to remove rights I otherwise had or accept unreasonable terms undermining my privacy, I choose away the service. I simply do not have the conscience to accept terms I have no indention of upholding. But how are the system and service providers to know how many people they scared away? Normally I just quietly walk away.