1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Google Chrome OS Developers Working On DRM Code

Google

Published on 09 August 2013 10:45 AM EDT
Written by Michael Larabel in Google
Comment On This Article

There doesn't appear to be much to get excited about right now, but it appears some Google developers working on Chrome/Chromium OS have begun working on some improvements to the Linux DRM (Direct Rendering Manager) kernel graphics drivers.

Hitting the DRI-devel mailing list this week is code from Google's Sean Paul for introducing a "drm_bridge" component to the DRM kernel subsystem.
This patch adds the notion of a drm_bridge. A bridge is a chained device which hangs off an encoder. The drm driver using the bridge should provide the association between encoder and bridge. Once a bridge is associated with an encoder, it will participate in mode set, dpms, and optionally connection detection.

Since a connector may not be able to determine the connection state downstream of the bridge, bridges may implement detect() which will take precedence over connector detect() if the bridge is already attached to an encoder and that encoder is already attached to the connector. In practical terms, this requires the drm driver to make these associations at init time, which is fine for SoC applications where this link is static.

This Linux kernel patch adds some new interfaces but doesn't change any existing mainline DRM driver in the 200 line patch. In a follow-up message, Nouveau founder turned Googler St├ęphane Marchesin wrote, "We have two bridges using it here, and we're working on adding a third. [Rob Clark with the Freedreno/Qualcomm driver] want to add one too."

It will be interesting to see what the Google Chrome OS developers are working on next as it concerns Linux graphics. In the past they worked a lot on Intel Gallium3D support to use the "i915g" driver for older Chromebooks. Let's hope this current DRM work is part of a grander plan. When it comes to the current ARM-based Google devices they seem to use the Samsung Exynos SoC that already has a basic open-source DRM driver and for their growing Qualcomm devices there's open-source driver work being done independently through Freedreno.

Latest Linux Hardware Reviews
  1. Overclocking The AMD AM1 Athlon & Sempron APUs
  2. AMD Athlon 5350 / 5150 & Sempron 3850 / 2650
  3. Upgraded Kernel & Mesa Yield A Big Boost For Athlon R3 Graphics
  4. AMD Athlon 5350 APU On Linux
Latest Linux Articles
  1. Are AMD Athlon/Sempron APUs Fast Enough For Steam On Linux?
  2. AMD Athlon's R3 Graphics: RadeonSI Gallium3D vs. Catalyst
  3. GCC 4.9 Compiler Optimization Benchmarks For Faster Binaries
  4. DDR3 Memory Scaling Performance With AMD's Athlon 5350
Latest Linux News
  1. Intel Broadwell GT3 Graphics Have Dual BSD Rings
  2. Early Linux 3.15 Benchmarks Of Intel Core i7 + Radeon
  3. Red Hat Releases Its RHEL 7 Release Candidate
  4. New Features Coming To Xubuntu 14.04 LTS
  5. NVIDIA Officially Releases CUDA 6
  6. Google Releases An AutoFDO Converter For Perf In LLVM
  7. Fedora 21 To Evaluate Remote Journal Logging, 64-bit ARM Emulation
  8. Star Citizen Will Be Coming To Linux
  9. Ubuntu 14.10 Convergence To Focus On Replacing Core Apps
  10. The Results Of Optimizing Radeon's VRAM Behavior
  11. Kernel Developers Discuss Improving Kernel Configurations
  12. Apple, LLVM Developers Figure Out Their 64-Bit ARM Approach
Latest Forum Discussions
  1. The GNOME Foundation Is Running Short On Money
  2. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  3. Bye bye BSD, Hello Linux: A Sys Admin's Story
  4. New tool for undervolt/overclock AMD K8L and K10 processors
  5. How to enable opengl 3.3 on r9 270?
  6. R290x sound problems
  7. radeon-profile: tool for changing profiles and monitoring some GPU parameters
  8. Torvalds Is Unconvinced By LTO'ing A Linux Kernel