[PATCH v5 4/7] video: add generic framebuffer eviction

2016-09-05 Thread Noralf Trønnes
Den 05.09.2016 13:19, skrev David Herrmann: > Hi > > On Sat, Sep 3, 2016 at 2:06 PM, Noralf Trønnes wrote: >> Den 02.09.2016 10:22, skrev David Herrmann: >>> There are several situations where we want hardware handover from an early >>> boot GFX driver (e.g., vgacon, vesafb, efifb, simplefb) to

[PATCH v5 4/7] video: add generic framebuffer eviction

2016-09-05 Thread David Herrmann
Hi On Sat, Sep 3, 2016 at 2:06 PM, Noralf Trønnes wrote: > > Den 02.09.2016 10:22, skrev David Herrmann: >> >> There are several situations where we want hardware handover from an early >> boot GFX driver (e.g., vgacon, vesafb, efifb, simplefb) to a full fletched >> GFX driver (e.g., most DRM dr

[PATCH v5 4/7] video: add generic framebuffer eviction

2016-09-03 Thread Noralf Trønnes
Den 02.09.2016 10:22, skrev David Herrmann: > There are several situations where we want hardware handover from an early > boot GFX driver (e.g., vgacon, vesafb, efifb, simplefb) to a full fletched > GFX driver (e.g., most DRM drivers). So far, we relied on > remove_conflicting_framebuffers() to d

[PATCH v5 4/7] video: add generic framebuffer eviction

2016-09-02 Thread Tom Gundersen
On Fri, Sep 2, 2016 at 10:22 AM, David Herrmann wrote: > There are several situations where we want hardware handover from an early > boot GFX driver (e.g., vgacon, vesafb, efifb, simplefb) to a full fletched > GFX driver (e.g., most DRM drivers). So far, we relied on > remove_conflicting_framebu

[PATCH v5 4/7] video: add generic framebuffer eviction

2016-09-02 Thread David Herrmann
There are several situations where we want hardware handover from an early boot GFX driver (e.g., vgacon, vesafb, efifb, simplefb) to a full fletched GFX driver (e.g., most DRM drivers). So far, we relied on remove_conflicting_framebuffers() to do this for us, however, this had a bunch of downsides