From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Rob Clark <rob.clark@linaro.org>
Cc: Greg KH <greg@kroah.com>,
linux-omap@vger.kernel.org, dri-devel@lists.freedesktop.org,
patches@linaro.org
Subject: Re: [PATCH] omap2+: add drm device
Date: Fri, 16 Mar 2012 13:03:45 +0200 [thread overview]
Message-ID: <1331895825.1653.15.camel@lappy> (raw)
In-Reply-To: <CAF6AEGtC9BA-8WZGNOs_rMFrzt88XPNjVRUooG7-Nxe7yDKjpA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1462 bytes --]
On Thu, 2012-03-15 at 07:32 -0500, Rob Clark wrote:
> On Thu, Mar 15, 2012 at 3:46 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > On Wed, 2012-03-14 at 10:06 -0500, Rob Clark wrote:
> >
> >> > Well, as I said, it's not an issue for me and from my side it can be
> >> > improved later.
> >>
> >> yeah, when CMA is actually merged, there are a few other things I'd
> >> like to do to, incl converting omapfb over to use CMA and remove
> >> omap_vram.. but I guess those will be other patches.
> >
> > Right, I just realized CMA is not in the kernel, nor does it seem to be
> > in the linux-next. Is there a reason why you want it already merged?
> > Wouldn't it be easier to get it in only when it can actually be used.
> > Especially if there's room for improvement.
>
> Some folks are already pulling CMA into product kernels for various
> reasons.. keeping this w/ #ifdef CONFIG_CMA guards seemed like it
> would make their life a bit easier.
>
> But if people feel strongly about it, I can strip that out.
Well, I wouldn't say "feel strongly", but... I think the mainline kernel
should have code only for the mainline kernel, not for some custom
kernels. And the code is not testable in any way, not even compilable. I
think all code going in should be tested and compiled. Also, if the CMA
code is not in, who says it won't change. Perhaps the CMA function won't
even exist in the version going into mainline.
Tomi
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-03-16 11:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 20:34 [PATCH] omap2+: add drm device Rob Clark
2012-03-14 12:38 ` Tomi Valkeinen
2012-03-14 12:55 ` Rob Clark
2012-03-14 13:07 ` Tomi Valkeinen
2012-03-14 13:16 ` Rob Clark
2012-03-14 13:43 ` Tomi Valkeinen
2012-03-14 15:06 ` Rob Clark
2012-03-15 8:46 ` Tomi Valkeinen
2012-03-15 12:32 ` Rob Clark
2012-03-16 11:03 ` Tomi Valkeinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-23 20:08 Andy Gross
2012-05-24 6:01 ` Tomi Valkeinen
2012-05-24 6:27 ` Clark, Rob
2012-05-24 7:05 ` Tomi Valkeinen
2012-05-24 7:21 ` Tomi Valkeinen
2012-05-24 8:44 ` Rob Clark
2012-05-24 12:13 ` Tomi Valkeinen
2012-05-24 15:09 ` Gross, Andy
2012-05-24 15:26 ` Tomi Valkeinen
2012-06-11 14:51 ` Gross, Andy
2012-06-11 14:54 ` Gross, Andy
2012-06-11 15:05 ` Tomi Valkeinen
2012-05-24 8:35 ` Rob Clark
2012-05-24 12:10 ` Tomi Valkeinen
2012-05-24 14:22 ` Gross, Andy
2012-06-11 15:51 ` Rob Clark
2012-06-19 21:12 ` Gross, Andy
2012-07-03 7:09 ` Tony Lindgren
2012-03-05 16:54 Rob Clark
2012-03-06 0:10 ` Tony Lindgren
2012-03-06 1:42 ` Rob Clark
2012-03-06 13:26 ` Tomi Valkeinen
2012-03-06 14:01 ` Rob Clark
2012-03-06 14:35 ` Tomi Valkeinen
2012-03-06 15:29 ` Rob Clark
2012-03-07 11:59 ` Tomi Valkeinen
2012-03-07 13:06 ` Rob Clark
2012-03-07 13:11 ` Tomi Valkeinen
2012-03-06 15:50 ` Gross, Andy
2012-03-07 12:05 ` Tomi Valkeinen
2012-03-07 13:27 ` Rob Clark
2012-03-07 15:59 ` Gross, Andy
2012-03-08 7:47 ` Tomi Valkeinen
2012-01-13 19:41 Rob Clark
2012-01-13 19:46 ` Rob Clark
2012-01-13 19:49 ` Felipe Contreras
2012-01-13 19:53 ` Rob Clark
2012-01-13 20:23 ` Felipe Contreras
2012-01-13 20:25 ` Rob Clark
2012-01-13 19:51 ` Aguirre, Sergio
2012-01-13 19:54 ` Rob Clark
2012-01-13 20:29 ` Felipe Contreras
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=1331895825.1653.15.camel@lappy \
--to=tomi.valkeinen@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=linux-omap@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rob.clark@linaro.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).