From: Denys Dmytriyenko <denys@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] libdrm: Add GLSDK specific staging tree for omap-a15
Date: Thu, 27 Jun 2013 15:17:48 -0400 [thread overview]
Message-ID: <20130627191748.GD30195@edge> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1015961D1CF@DLEE11.ent.ti.com>
On Thu, Jun 27, 2013 at 05:46:43PM +0000, Maupin, Chase wrote:
> >-----Original Message-----
> >From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> >bounces@yoctoproject.org] On Behalf Of Heroor, Siddharth
> >Sent: Thursday, June 27, 2013 12:17 PM
> >To: meta-ti@yoctoproject.org
> >Subject: [meta-ti] [PATCH] libdrm: Add GLSDK specific staging tree
> >for omap-a15
> >
> >* Override SRC_URI to use TI's tree at
> >https://git.ti.com/glsdk/libdrm
> > This tree includes patches on top of the upstream libdrm for
> > omap5 and dra7xx class of devices.
> >
> >Signed-off-by: Mrinmayee Hingolikar <mrinmayee@ti.com>
> >Signed-off-by: Siddharth Heroor <heroor@ti.com>
> >---
> > recipes-graphics/drm/libdrm_2.4.41.bb | 15 +++++++++++++++
> > 1 files changed, 15 insertions(+), 0 deletions(-)
> > create mode 100644 recipes-graphics/drm/libdrm_2.4.41.bb
> >
> >diff --git a/recipes-graphics/drm/libdrm_2.4.41.bb b/recipes-
> >graphics/drm/libdrm_2.4.41.bb
> >new file mode 100644
> >index 0000000..31f7cee
> >--- /dev/null
> >+++ b/recipes-graphics/drm/libdrm_2.4.41.bb
>
> I thought you were going to bbappend this instead of overlaying the whole
> recipe.
I was confused at first as well, but I guess it should be fine, considering
there's no 2.4.41 version to bbapend anyway.
> >@@ -0,0 +1,15 @@
> >+require recipes-graphics/drm/libdrm.inc
> >+
> >+COMPATIBLE_MACHINE = "omap-a15"
> >+
> >+DEFAULT_PREFERENCE = "-1"
> >+
> >+EXTRA_OECONF += "--enable-omap-experimental-api"
> >+
> >+SRC_URI = "git://git.ti.com/glsdk/libdrm.git;protocol=git"
> >+SRCREV = "3cb5405084111193cedb8796d259b56560b088f0"
> >+
> >+# Append to the PR so that a new SRCREV will cause a rebuild
> >+PR_append = "a+gitr${SRCPV}"
>
> I always had issue with this. I'm not sure that this statement holds true
> because whether a new SRCREV will cause a rebuild would depend on whether
> that SRCREV sorts higher than the old one. Unless something else has
> changed. This is useful though if you want to know what SRCREV was used for
> a build.
Well, if every time you update SRCREV you also increment the first letter, it
will work as expected - so the comment is kind of correct... :)
> That being said if you were going to overlay this recipe the PR should be
> something like
>
> PR = "${INC_PR}.0"
>
> Right now you are appending to the default since PR is not defined. With a
> bbappend you should append a -arago flag.
>
> So this comes back to why no bbappend? Is it because the base version in
> oe-core is 2.4.39 and not 2.4.41? Can you not append the _git version of
> the recipe and update the PV appropriately?
>
> >+
> >+S = "${WORKDIR}/git"
> >--
> >1.7.0.4
> >
> >_______________________________________________
> >meta-ti mailing list
> >meta-ti@yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/meta-ti
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2013-06-27 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 17:16 [PATCH] libdrm: Add GLSDK specific staging tree for omap-a15 Siddharth Heroor
2013-06-27 17:46 ` Maupin, Chase
2013-06-27 19:17 ` Denys Dmytriyenko [this message]
2013-06-28 9:16 ` Siddharth Heroor
2013-06-28 9:48 ` Siddharth Heroor
2013-06-28 11:25 ` Maupin, Chase
2013-06-28 13:38 ` Siddharth Heroor
2013-07-01 4:51 ` Denys Dmytriyenko
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=20130627191748.GD30195@edge \
--to=denys@ti.com \
--cc=chase.maupin@ti.com \
--cc=meta-ti@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.