linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx_v6_v7_defconfig: Enable GPU support
Date: Tue, 22 Dec 2015 13:47:34 +0100	[thread overview]
Message-ID: <1450788454.2637.17.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5A8BEkNvrazmksRBRUQw+4mWwbfKtrK6KzD3XK5L5Fs7w@mail.gmail.com>

Am Dienstag, den 22.12.2015, 10:30 -0200 schrieb Fabio Estevam:
> On Tue, Dec 22, 2015 at 10:21 AM, Shawn Guo <shawnguo@kernel.org>
> wrote:
> 
> > I do not have this Kconfig option on my tree yet.
> 
> Yes, I know, but would this cause any issue?
> 
> This would allow etnaviv to be functional by default on 4.5.
> Otherwise
> we should wait for 4.6.
> 
I don't see a need to rush this. We can always enable it in the -rc
phase of 4.5 is we desire.
But to be honest I would like to give etnaviv a cycle to stabilize
until we enable it by default. With i.MX6QP now hitting the street and
basically no testing of etnaviv being done there until now, I would
rather not have it in the defconfig just now. It's not like it's hard
for people willing to test this to enable a single Kconfig option...

Regards,
Lucas

  reply	other threads:[~2015-12-22 12:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 18:44 [PATCH] ARM: imx_v6_v7_defconfig: Enable GPU support Fabio Estevam
2015-12-22 12:21 ` Shawn Guo
2015-12-22 12:30   ` Fabio Estevam
2015-12-22 12:47     ` Lucas Stach [this message]
2015-12-22 12:51       ` Fabio Estevam
2015-12-22 12:53       ` Russell King - ARM Linux
2015-12-22 15:02         ` Russell King - ARM Linux
2015-12-22 15:31           ` Fabio Estevam
2015-12-22 16:16             ` Russell King - ARM Linux
2015-12-22 16:38               ` Fabio Estevam
2015-12-22 17:34                 ` Jon Nettleton

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=1450788454.2637.17.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).