linux-kernel - Re: [PATCH v2 05/10] video: add MIPI DSI host controller bridge

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: <20180302185759.GA114194@rodete-desktop-imager.corp.google.com>
Date:   Fri, 2 Mar 2018 10:58:01 -0800
From:   Brian Norris <briannorris@...omium.org>
To:     yannick fertre <yannick.fertre@...com>
Cc:     Vikas Manocha <vikas.manocha@...com>,
        Benjamin Gaignard <benjamin.gaignard@...aro.org>,
        Philippe Cornu <philippe.cornu@...com>,
        Patrice Chotard <patrice.chotard@...com>,
        Patrick DELAUNAY <patrick.delaunay@...com>,
        Christophe KERELLO <christophe.kerello@...com>,
        Archit Taneja <architt@...eaurora.org>,
        Andrzej Hajda <a.hajda@...sung.com>,
        Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
        David Airlie <airlied@...ux.ie>,
        Bhumika Goyal <bhumirks@...il.com>,
        Gustavo Padovan <gustavo@...ovan.org>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Sean Paul <seanpaul@...omium.org>,
        Albert Aribaud <albert.u.boot@...baud.net>,
        Simon Glass <sjg@...omium.org>,
        Anatolij Gustschin <agust@...x.de>,
        Thierry Reding <thierry.reding@...il.com>,
        u-boot@...ts.denx.de, dri-devel@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 05/10] video: add MIPI DSI host controller bridge

Hi,

On Fri, Mar 02, 2018 at 04:44:06PM +0100, yannick fertre wrote:
> Add a Synopsys Designware MIPI DSI host bridge driver, based on the
> Rockchip version from rockchip/dw-mipi-dsi.c with phy & bridge APIs.

How many times are we going to allow copy-and-pasting the same driver?
Last time we wanted to modify the Rockchip driver, we were told
"consolidate", because ST had already forked our driver. This nearly
halted all progress. I'm going to be real disappointed if we see another
fork get merged.

(IOW, I would say "over my dead body," but I have no power here.)

And why can't you use DRM?

Brian