From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932379AbdBPMxO (ORCPT ); Thu, 16 Feb 2017 07:53:14 -0500 Received: from smtp.math.uni-bielefeld.de ([129.70.45.10]:37547 "EHLO smtp.math.uni-bielefeld.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754980AbdBPMxM (ORCPT ); Thu, 16 Feb 2017 07:53:12 -0500 X-Greylist: delayed 602 seconds by postgrey-1.27 at vger.kernel.org; Thu, 16 Feb 2017 07:53:11 EST To: ML dri-devel Cc: maxime.ripard@free-electrons.com, Rob Herring , Mark Rutland , wens@csie.org, Greg Kroah-Hartman , thomas.petazzoni@free-electrons.com, devicetree@vger.kernel.org, linux-kernel , linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org From: Tobias Jakobi Subject: Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements Message-ID: <10fd28cb-269a-ec38-ecfb-b7c86be3e716@math.uni-bielefeld.de> Date: Thu, 16 Feb 2017 13:43:06 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, I was wondering about the following. Wasn't there some strict requirement about code going upstream, which also included that there was a full open-source driver stack for it? I don't see how this is the case for Mali, neither in the kernel, nor in userspace. I'm aware that the Mali kernel driver is open-source. But it is not upstream, maintained out of tree, and won't land upstream in its current form (no resemblence to a DRM driver at all). And let's not talk about the userspace part. So, why should this be here? With best wishes, Tobias P.S.: I'm signed up to dri-devel in digest mode, so sorry if this mail doesn't properly show up in the corresponding ml thread.