linux-kernel - Re: [PATCH v8 11/11] drm: sti: Add DRM driver itself

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKMK7uGcFhfzeNTPNk=X_N=C4pda0LTtsb51JLGNBZAU5kg6tg@mail.gmail.com>
Date:	Wed, 30 Jul 2014 21:48:27 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Benjamin Gaignard <benjamin.gaignard@...aro.org>
Cc:	dri-devel <dri-devel@...ts.freedesktop.org>,
	"linaro-mm-sig@...ts.linaro.org" <linaro-mm-sig@...ts.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Airlie <airlied@...ux.ie>
Subject: Re: [PATCH v8 11/11] drm: sti: Add DRM driver itself

On Wed, Jul 30, 2014 at 7:42 PM, Benjamin Gaignard
<benjamin.gaignard@...aro.org> wrote:
> @@ -87,11 +90,50 @@ static int sti_compositor_bind(struct device *dev, struct device *master,
>         struct sti_compositor *compo = dev_get_drvdata(dev);
>         struct drm_device *drm_dev = data;
>         unsigned int i, crtc = 0, plane = 0;
> +       struct sti_drm_private *dev_priv = drm_dev->dev_private;
> +       struct drm_plane *cursor = NULL;
> +       struct drm_plane *primary = NULL;
> +
> +       dev_priv->compo = compo;
>
>         drm_vblank_init(drm_dev, crtc);


This looks strange - you should pass this the total number of crtcs
(the same that eventually ends up in dev->mode_config.num_crtc), not
0. And the assignement of cursors to crtcs looks a bit strange on
first read-through, but I have no clue about the sti hw. And in any
case those pointers really only matter for backwards compat with
existing pageflip and cursor ioctls, so doesn't really matter too
much.

Anyway didn't spot anything else which would need to be upgrade to
never kms interfaces, so ack from my side for that. Only looked at
that since right now I'm refreshing drm docs in those areas ;-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/