[Intel-gfx] [PATCH] drm/doc: Update todo.rst
Sean Paul
seanpaul at chromium.org
Mon Sep 11 18:58:36 UTC 2017
On Mon, Sep 11, 2017 at 08:51:51AM +0200, Daniel Vetter wrote:
> We're using this for outreachy, unfortunately someone already tried to
> look at a task that was done already :-(
>
> Update them all.
>
> Cc: Sean Paul <seanpaul at chromium.org>
> Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>
Applied to -misc-next
Thanks!
Sean
> ---
> Documentation/gpu/todo.rst | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index 22af55d06ab8..850ba459da11 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -75,17 +75,6 @@ helpers.
>
> Contact: Ville Syrjälä, Daniel Vetter, driver maintainers
>
> -Implement deferred fbdev setup in the helper
> ---------------------------------------------
> -
> -Many (especially embedded drivers) want to delay fbdev setup until there's a
> -real screen plugged in. This is to avoid the dreaded fallback to the low-res
> -fbdev default. Many drivers have a hacked-up (and often broken) version of this,
> -better to do it once in the shared helpers. Thierry has a patch series, but that
> -one needs to be rebased and final polish applied.
> -
> -Contact: Thierry Reding, Daniel Vetter, driver maintainers
> -
> Convert early atomic drivers to async commit helpers
> ----------------------------------------------------
>
> @@ -138,6 +127,8 @@ interfaces to fix these issues:
> the acquire context explicitly on stack and then also pass it down into
> drivers explicitly so that the legacy-on-atomic functions can use them.
>
> + Except for some driver code this is done.
> +
> * A bunch of the vtable hooks are now in the wrong place: DRM has a split
> between core vfunc tables (named ``drm_foo_funcs``), which are used to
> implement the userspace ABI. And then there's the optional hooks for the
> @@ -151,6 +142,8 @@ interfaces to fix these issues:
> connector at runtime. That's almost all of them, and would allow us to get
> rid of a lot of ``best_encoder`` boilerplate in drivers.
>
> + This was almost done, but new drivers added a few more cases again.
> +
> Contact: Daniel Vetter
>
> Get rid of dev->struct_mutex from GEM drivers
> --
> 2.14.1
>
--
Sean Paul, Software Engineer, Google / Chromium OS
More information about the Intel-gfx
mailing list