kernel-packages team mailing list archive

[Timo Aaltonen <tjaalton@xxxxxxxxxx>]

Public bug reported:

Upstream i915 code has been feature-frozen for drm-next, and rebasing
i915_bpo to it is fairly simple. We need all the drm_atomic* changes to
date though, in order to avoid oopses loading the driver. Thankfully
i915_bpo is the only driver that uses them, so there's no chance of
regressing other drivers.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: linux (Ubuntu Vivid)
     Importance: High
     Assignee: Timo Aaltonen (tjaalton)
         Status: Triaged

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Vivid)
       Status: New => Triaged

** Changed in: linux (Ubuntu)
       Status: New => Invalid

** Changed in: linux (Ubuntu Vivid)
     Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460674

Title:
  [i915_bpo] Rebase driver to 4.2~pre

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Triaged

Bug description:
  Upstream i915 code has been feature-frozen for drm-next, and rebasing
  i915_bpo to it is fairly simple. We need all the drm_atomic* changes
  to date though, in order to avoid oopses loading the driver.
  Thankfully i915_bpo is the only driver that uses them, so there's no
  chance of regressing other drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460674/+subscriptions