1. 02 May, 2013 36 commits
  2. 01 May, 2013 4 commits
    • Dave Airlie's avatar
      drm/cirrus: deal with bo reserve fail in dirty update path · f3b2bbdc
      Dave Airlie authored
      
      
      Port over the mgag200 fix to cirrus as it suffers the same issue.
      
          On F19 testing, it was noticed we get a lot of errors in dmesg
          about being unable to reserve the buffer when plymouth starts,
          this is due to the buffer being in the process of migrating,
          so it makes sense we can't reserve it.
      
          In order to deal with it, this adds delayed updates for the dirty
          updates, when the bo is unreservable, in the normal console case
          this shouldn't ever happen, its just when plymouth or X is
          pushing the console bo to system memory.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      f3b2bbdc
    • Dave Airlie's avatar
      drm/ast: deal with bo reserve fail in dirty update path · 306373b6
      Dave Airlie authored
      
      
      Port over the mgag200 fix to ast as it suffers the same issue.
      
          On F19 testing, it was noticed we get a lot of errors in dmesg
          about being unable to reserve the buffer when plymouth starts,
          this is due to the buffer being in the process of migrating,
          so it makes sense we can't reserve it.
      
          In order to deal with it, this adds delayed updates for the dirty
          updates, when the bo is unreservable, in the normal console case
          this shouldn't ever happen, its just when plymouth or X is
          pushing the console bo to system memory.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      306373b6
    • Dave Airlie's avatar
      drm/mgag200: deal with bo reserve fail in dirty update path · 64171959
      Dave Airlie authored
      
      
      On F19 testing, it was noticed we get a lot of errors in dmesg
      about being unable to reserve the buffer when plymouth starts,
      this is due to the buffer being in the process of migrating,
      so it makes sense we can't reserve it.
      
      In order to deal with it, this adds delayed updates for the dirty
      updates, when the bo is unreservable, in the normal console case
      this shouldn't ever happen, its just when plymouth or X is
      pushing the console bo to system memory.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      64171959
    • Dave Airlie's avatar
      drm/i915: fix dmabuf vmap support · b11b88ef
      Dave Airlie authored
      
      
      Sometimes that extra semicolon can really be hard to spot.
      Acked-by: default avatarImre Deak <imre.deak@intel.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      b11b88ef