All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Etheridge, Darren" <detheridge@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH 1/2] branding-glsdk: pin to GLSDK libdrm version
Date: Wed, 5 Feb 2014 14:24:26 -0500	[thread overview]
Message-ID: <20140205192425.GU18784@edge> (raw)
In-Reply-To: <1A80A2FD7F34484786E5DF71F3968B6941E8B45D@DLEE10.ent.ti.com>

All,

What is the consensus here? I see that GLSDK uses own libdrm which is based on 
2.4.41, but is fetched from git.ti.com (the recipe is in meta-ti), while for 
AM335x mostly we'd like to update libdrm to the latest upstream... Is use of 
branding an optimal solution here?

-- 
Denys


On Tue, Feb 04, 2014 at 10:43:21AM -0500, Etheridge, Darren wrote:
> Actually devices like AM335x (DRA7x works with existing libdrm version, 
> although 2.4.41 is a year old now):
> 
> Two reasons for needing the version bump:
> 1) tilcdc DRM device is supported (this commit - 
> http://cgit.freedesktop.org/mesa/drm/commit/?id=6e8f868e034531b66a215e4e6d978b43b58b92d0)
> 2) Pixel type of XB24 is supported in modetest (this is the correct pixel 
> ordering for AM335x hardware added here: 
> http://cgit.freedesktop.org/mesa/drm/commit/?id=fa2925aa342158037ef972f3ef095442fb1fe430)
> 
> 
> Darren
> 
> > -----Original Message-----
> > From: Maupin, Chase
> > Sent: Tuesday, February 04, 2014 7:17 AM
> > To: Hingolikar, Mrinmayee; Dmytriyenko, Denys; Etheridge, Darren
> > Cc: meta-arago@arago-project.org
> > Subject: RE: [meta-arago] [PATCH 1/2] branding-glsdk: pin to GLSDK libdrm
> > version
> > 
> > Mrinmayee,
> > 
> > What is in your 2.4.41 version that makes you need to pin there.  I ask
> > because Darren has reported needing a newer version to work properly with
> > devices like DRA7xx.
> > 
> > >-----Original Message-----
> > >From: Hingolikar, Mrinmayee
> > >Sent: Tuesday, February 04, 2014 5:05 AM
> > >To: Dmytriyenko, Denys; Maupin, Chase
> > >Cc: meta-arago@arago-project.org
> > >Subject: RE: [meta-arago] [PATCH 1/2] branding-glsdk: pin to GLSDK
> > >libdrm version
> > >
> > >Hi all,
> > >
> > >The libdrm in GLSDK is based on the 2.4.41 version from upstream.
> > >A preferred version is required since a 2.4.42 version is present
> > >in oe-core.
> > >
> > >
> > >Regards,
> > >Mrinmayee
> > >
> > >> -----Original Message-----
> > >> From: Dmytriyenko, Denys
> > >> Sent: Tuesday, February 04, 2014 6:21 AM
> > >> To: Maupin, Chase
> > >> Cc: meta-arago@arago-project.org; Hingolikar, Mrinmayee
> > >> Subject: Re: [meta-arago] [PATCH 1/2] branding-glsdk: pin to
> > >GLSDK
> > >> libdrm version
> > >>
> > >> Ping
> > >>
> > >> On Fri, Jan 31, 2014 at 07:50:39PM +0000, Maupin, Chase wrote:
> > >> > Mrinmayee,
> > >> >
> > >> > Can you comment on the below need for 2.4.41?
> > >> >
> > >> > >-----Original Message-----
> > >> > >From: Maupin, Chase
> > >> > >Sent: Friday, January 31, 2014 1:48 PM
> > >> > >To: meta-arago@arago-project.org
> > >> > >Cc: Maupin, Chase
> > >> > >Subject: [PATCH 1/2] branding-glsdk: pin to GLSDK libdrm
> > >version
> > >> > >
> > >> > >* The GLSDK prefers to use the 2.4.41 version of libdrm from
> > >> > >  meta-ti so pin that version in the branding file.
> > >> > >
> > >> > >Signed-off-by: Chase Maupin <chase.maupin@ti.com>
> > >> > >---
> > >> > > .../conf/distro/include/branding-glsdk.inc         |    4
> > >++++
> > >> > > 1 file changed, 4 insertions(+)
> > >> > >
> > >> > >diff --git a/meta-arago-distro/conf/distro/include/branding-
> > >> > >glsdk.inc b/meta-arago-distro/conf/distro/include/branding-
> > >> > >glsdk.inc
> > >> > >index d1c30f3..b33b21d 100644
> > >> > >--- a/meta-arago-distro/conf/distro/include/branding-
> > >glsdk.inc
> > >> > >+++ b/meta-arago-distro/conf/distro/include/branding-
> > >glsdk.inc
> > >> > >@@ -2,3 +2,7 @@
> > >> > >
> > >> > > # Use the SDK supported kernel and kernel version
> > >> > > PREFERRED_PROVIDER_virtual/kernel = "linux-ti-glsdk"
> > >> > >+
> > >> > >+# Set the PREFERRED_VERSION of libdrm to the glsdk version
> > >for
> > >> > >the
> > >> > >+# glsdk branded builds
> > >> > >+PREFERRED_VERSION_libdrm = "2.4.41"
> > >> > >--
> > >> > >1.7.9.5
> > >> >
> > >> > _______________________________________________
> > >> > meta-arago mailing list
> > >> > meta-arago@arago-project.org
> > >> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2014-02-05 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 19:48 [PATCH 1/2] branding-glsdk: pin to GLSDK libdrm version Chase Maupin
2014-01-31 19:48 ` [PATCH 2/2] arago-prefs: set PREFERRED VERSION of libdrm to latest Chase Maupin
2014-02-28 20:10   ` Denys Dmytriyenko
2014-02-28 22:24     ` Maupin, Chase
2014-01-31 19:50 ` [PATCH 1/2] branding-glsdk: pin to GLSDK libdrm version Maupin, Chase
2014-02-04  0:51   ` Denys Dmytriyenko
2014-02-04 10:04     ` Hingolikar, Mrinmayee
2014-02-04 13:16       ` Maupin, Chase
2014-02-04 15:43         ` Etheridge, Darren
2014-02-05 19:24           ` Denys Dmytriyenko [this message]
2014-02-05 22:08             ` Maupin, Chase

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=20140205192425.GU18784@edge \
    --to=denys@ti.com \
    --cc=detheridge@ti.com \
    --cc=meta-arago@arago-project.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.