mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: ML dri-devel <dri-devel@lists.freedesktop.org>
Cc: maxime.ripard@free-electrons.com,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	wens@csie.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	thomas.petazzoni@free-electrons.com, devicetree@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements
Date: Thu, 16 Feb 2017 13:43:06 +0100	[thread overview]
Message-ID: <10fd28cb-269a-ec38-ecfb-b7c86be3e716@math.uni-bielefeld.de> (raw)

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.

             reply	other threads:[~2017-02-16 12:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 12:43 Tobias Jakobi [this message]
2017-02-16 16:54 ` Emil Velikov
2017-02-17 15:44   ` Maxime Ripard
2017-02-17 20:39     ` Emil Velikov
2017-02-24  0:19       ` Maxime Ripard
2017-02-26 12:14         ` Emil Velikov
2017-02-17 21:56     ` Rask Ingemann Lambertsen
2017-02-16 18:45 ` Maxime Ripard
2017-02-17 12:45   ` Tobias Jakobi
2017-02-17 13:20     ` Emil Velikov
2017-02-17 15:42     ` Alexandre Belloni
2017-02-17 15:56       ` Tobias Jakobi
2017-02-24 13:56         ` Rob Herring
2017-02-17 15:43     ` Maxime Ripard
2017-02-20 16:49       ` Thierry Reding
2017-02-23  0:44         ` Maxime Ripard
  -- strict thread matches above, loose matches on Subject: below --
2017-02-09 16:39 Maxime Ripard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10fd28cb-269a-ec38-ecfb-b7c86be3e716@math.uni-bielefeld.de \
    --to=tjakobi@math.uni-bielefeld.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=wens@csie.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®