Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • topic/drm-misc-2016-04-01
  • drm-intel-next-2016-03-30
    - VBT code refactor for a clean split between parsing&using of firmware
      information (Jani)
    - untangle the pll computation code, and splitting up the monster
      i9xx_crtc_compute_clocks (Ander)
    - dsi support for bxt (Jani, Shashank Sharma and others)
    - color manager (i.e. de-gamma, color conversion matrix & gamma support) from
      Lionel Landwerlin
    - Vulkan hsw support in the command parser (Jordan Justen)
    - large-scale renaming of intel_engine_cs variables/parameters to avoid the epic
      ring vs. engine confusion introduced in gen8 (Tvrtko Ursulin)
    - few atomic patches from Maarten&Matt, big one is two-stage wm programming on ilk-bdw
    - refactor driver load and add infrastructure to inject load failures for
      testing, from Imre
    - various small things all over
  • v4.6-rc1
    f55532a0 · Linux 4.6-rc1 ·
    Linux 4.6-rc1
    
  • iommu-updates-v4.6
    IOMMU Updates for Linux v4.6
    
    This time with:
    
    	* Updates for the Exynos IOMMU driver to make use of default
    	  domains and to add support for the SYSMMU v5
    
    	* New Mediatek IOMMU driver
    
    	* Support for the ARMv7 short descriptor format in the
    	  io-pgtable code
    
    	* Default domain support for the ARM SMMU
    
    	* Couple of other small fixes all over the place
    
  • topic/drm-misc-2016-03-22
  • v3.4.111
    3389604d · Linux 3.4.111 ·
    This is the 3.4.111 stable release
    
  • v3.12.57
    d9d35182 · Linux 3.12.57 ·
    This is the 3.12.57 stable release
    
  • v4.1.20
    7f307376 · Linux 4.1.20 ·
    Linux 4.1.20
    
  • v3.18.29
    d439e869 · Linux 3.18.29 ·
    Linux 3.18.29
    
  • gpio-v4.6-1
    This is the bulk of GPIO changes for kernel v4.6:
    
    Core changes:
    
    - The gpio_chip is now a *real device*. Until now the gpio chips
      were just piggybacking the parent device or (gasp) floating in
      space outside of the device model. We now finally make GPIO chips
      devices. The gpio_chip will create a gpio_device which contains
      a struct device, and this gpio_device struct is kept private.
      Anything that needs to be kept private from the rest of the kernel
      will gradually be moved over to the gpio_device.
    
    - As a result of making the gpio_device a real device, we have added
      resource management, so devm_gpiochip_add_data() will cut down on
      overhead and reduce code lines. A huge slew of patches convert
      almost all drivers in the subsystem to use this.
    
    - Building on making the GPIO a real device, we add the first step
      of a new userspace ABI: the GPIO character device. We take small
      steps here, so we first add a pure *information* ABI and the tool
      "lsgpio" that will list all GPIO devices on the system and all
      lines on these devices. We can now discover GPIOs properly from
      userspace. We still have not come up with a way to actually *use*
      GPIOs from userspace.
    
    - To encourage people to use the character device for the future,
      we have it always-enabled when using GPIO. The old sysfs ABI is
      still opt-in (and can be used in parallel), but is marked as
      deprecated. We will keep it around for the foreseeable future,
      but it will not be extended to cover ever more use cases.
    
    Cleanup:
    
    - Bjorn Helgaas removed a whole slew of per-architecture <asm/gpio.h>
      includes. This dates back to when GPIO was an opt-in feature and
      no shared library even existed: just a header file with proper
      prototypes was provided and all semantics were up to the arch to
      implement. These patches make the GPIO chip even more a proper
      device and cleans out leftovers of the old in-kernel API here
      and there. Still some cruft is left but it's very little now.
    
    - There is still some clamping of return values for .get() going
      on, but we now return sane values in the vast majority of drivers
      and the errorpath is sanitized. Some patches for powerpc, blackfin
      and unicore still drop in.
    
    - We continue to switch the ARM, MIPS, blackfin, m68k local GPIO
      implementations to use gpiochip_add_data() and cut down on code
      lines.
    
    - MPC8xxx is converted to use the generic GPIO helpers.
    
    - ATH79 is converted to use the generic GPIO helpers.
    
    New drivers:
    
    - WinSystems WS16C48
    
    - Acces 104-DIO-48E
    
    - F81866 (a F7188x variant)
    
    - Qoric (a MPC8xxx variant)
    
    - TS-4800
    
    - SPI serializers (pisosr): simple 74xx shift registers connected
      to SPI to obtain a dirt-cheap output-only GPIO expander.
    
    - Texas Instruments TPIC2810
    
    - Texas Instruments TPS65218
    
    - Texas Instruments TPS65912
    
    - X-Gene (ARM64) standby GPIO controller
    
  • v4.4.6
    0d191230 · Linux 4.4.6 ·
    This is the 4.4.6 stable release
    
  • v3.14.65
    dfbed80c · Linux 3.14.65 ·
    This is the 3.14.65 stable release
    
  • v3.10.101
    326a1b2d · Linux 3.10.101 ·
    This is the 3.10.101 stable release
    
  • media/v4.6-1
    media updates for v4.6-rc1
    
  • asoc-v4.6
    ASoC: Updates for v4.6
    
    The main thing in terms of the core this time around has been some
    additional framework work for dynamic topologies (though we *still*
    don't appear to have a stable ABI for the topology code, it's probably
    worth considering if this will ever happen...).  Otherwise the work has
    almost all been in the drivers:
    
     - HDMI support for Sky Lake, along with other fixes and enhancements
       for the Intel drivers.
     - Lots of improvements to the Renesas drivers.
     - Capture support for Qualcomm drivers.
     - Support for TI DaVinci DRA7xxx devices.
     - New machine drivers for Freescale systems with Cirrus CODECs,
       Mediatek systems with RT5650 CODECs.
     - New CPU drivers for Allwinner S/PDIF controllers
     - New CODEC drivers for Maxim MAX9867 and MAX98926 and Realtek RT5514.
    
  • drm-intel-next-fixes-2016-03-16
  • drm-intel-next-2016-03-14
    - two-stage wm updates for ilk-style platforms (Matt)
    - more wm work and fixes from Maarten&Ville
    - more work on rotated framebuffers to prep for rotated nv12 (Ville)
    - more dc fixes (Imre)
    - various execlist patches from Tvrtko
    - various clock cleanups for gmch from Ville
    - extract intel_dpll_mgr.c and refactor shared dpll code (Ander)
  • v4.5
    b562e44f · Linux 4.5 ·
    Linux 4.5
    
  • topic/drm-misc-2016-03-14
  • v2.6.32.71
    2896b357 · Linux 2.6.32.71 ·
    This is the 2.6.32.71 stable release