remarkable-linux/drivers/gpu/drm/cirrus
Dave Airlie f3b2bbdc8a drm/cirrus: deal with bo reserve fail in dirty update path
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: Dave Airlie <airlied@redhat.com>
2013-05-02 12:46:56 +10:00
..
cirrus_drv.c Drivers: gpu: remove __dev* attributes. 2013-01-03 15:57:15 -08:00
cirrus_drv.h drm/cirrus: deal with bo reserve fail in dirty update path 2013-05-02 12:46:56 +10:00
cirrus_fbdev.c drm/cirrus: deal with bo reserve fail in dirty update path 2013-05-02 12:46:56 +10:00
cirrus_main.c drm/<drivers>: Unified handling of unimplemented fb->create_handle 2013-01-20 15:57:57 +01:00
cirrus_mode.c UAPI: (Scripted) Convert #include "..." to #include <path/...> in drivers/gpu/ 2012-10-02 18:01:07 +01:00
cirrus_ttm.c drm/cirrus: deal with bo reserve fail in dirty update path 2013-05-02 12:46:56 +10:00
Kconfig drivers/gpu/drm/cirrus: remove depends on CONFIG_EXPERIMENTAL 2013-01-17 12:11:26 -08:00
Makefile drm/kms: driver for virtual cirrus under qemu 2012-05-17 11:02:24 +01:00