All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Andrea Galbusera <gizero@gmail.com>
Cc: meta-ti@yoctoproject.org, Arago Project git <git@arago-project.org>
Subject: Re: Denys Dmytriyenko : linux: remove old and outdated kernel recipes and configs
Date: Wed, 13 Apr 2016 16:38:14 -0400	[thread overview]
Message-ID: <20160413203814.GF10048@edge> (raw)
In-Reply-To: <CAC+thW1YUq9_xg2ubfhu2Yb+dcwTSnwTVrVj9_GGY=SwM1Q3hA@mail.gmail.com>

On Mon, Apr 04, 2016 at 11:58:57AM +0200, Andrea Galbusera wrote:
> Hi,
> 
> On Fri, Apr 1, 2016 at 8:40 PM, Arago Project git <git@arago-project.org> wrote:
> > Module: meta-ti
> > Branch: master
> > Commit: 8bb3fd849c8a43a9f9a4b26b820fd8553e01e0c7
> > URL:    http://arago-project.org/git/meta-ti.git?a=commit;h=8bb3fd849c8a43a9f9a4b26b820fd8553e01e0c7
> >
> > Author: Denys Dmytriyenko <denys@ti.com>
> > Date:   Thu Mar 31 21:53:58 2016 +0000
> >
> > linux: remove old and outdated kernel recipes and configs
> 
> This patch seems to break the build at least for some machines, which
> still prefer such outdated kernel recipes. This is the case i.e. for
> those machines that include either conf/machine/include/davinci.inc or
> conf/machine/include/omap3.inc. Just noticed it while trying to build
> a basic image for omap-l138 for a possible revamp of an old
> arago-based project. What are the plans for those machine? Are they in
> the way to be dropped? What's the suggested layer stack to start from
> for a "modern" system for an l138 system?

I guess I can point those machines to linux-ti-staging.

Of course, if one still needs the original kernel support for those platforms, 
the best approach is to use one of the old branches that had it - mixing very 
old kernel with a new system components is just asking for trouble.

Otherwise using either latest linux-ti-staging or even mainline would be 
recommended. Especially since there's some (although "best effort") work being 
done to update kernel support for those outdated platforms by adding Device 
Tree support etc...

-- 
Denys


> > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> >
> > ---
> >
> >  recipes-kernel/linux/linux-keystone-3.13/defconfig |    1 -
> >  recipes-kernel/linux/linux-keystone-rt/defconfig   |    1 -
> >  recipes-kernel/linux/linux-keystone-rt_3.10.bb     |   33 -----
> >  recipes-kernel/linux/linux-keystone/defconfig      |    1 -
> >  recipes-kernel/linux/linux-keystone_3.10.bb        |   33 -----
> >  recipes-kernel/linux/linux-keystone_3.13.bb        |   34 -----
> >  recipes-kernel/linux/linux-mainline/defconfig      |    1 -
> >  recipes-kernel/linux/linux-mainline_3.14.bb        |   41 ------
> >  recipes-kernel/linux/linux-ti-glsdk/defconfig      |    1 -
> >  recipes-kernel/linux/linux-ti-glsdk_3.8.bb         |   32 -----
> >  .../linux/linux-ti-staging-3.14/configs/systest    |    1 -
> >  .../linux/linux-ti-staging-3.14/defconfig          |    1 -
> >  recipes-kernel/linux/linux-ti-staging_3.14.bb      |   67 ----------
> >  recipes-kernel/linux/multi-kernel.inc              |  140 --------------------
> >  .../linux/sitara-linux-ti-staging-3.14/defconfig   |    1 -
> >  .../linux/sitara-linux-ti-staging_3.14.bb          |   51 -------
> >  16 files changed, 0 insertions(+), 439 deletions(-)
> >
> > Diff:   http://arago-project.org/git/meta-ti.git?a=commitdiff;h=8bb3fd849c8a43a9f9a4b26b820fd8553e01e0c7
> > --
> > _______________________________________________
> > 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


      reply	other threads:[~2016-04-13 20:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 18:40 Denys Dmytriyenko : linux: remove old and outdated kernel recipes and configs Arago Project git
2016-04-04  9:58 ` Andrea Galbusera
2016-04-13 20:38   ` Denys Dmytriyenko [this message]

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=20160413203814.GF10048@edge \
    --to=denys@ti.com \
    --cc=git@arago-project.org \
    --cc=gizero@gmail.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.