Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
	Mark Hatle <mark.hatle@windriver.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU
Date: Fri, 01 Jun 2018 23:45:04 +0100	[thread overview]
Message-ID: <1527893104.19847.8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=Wu5v1VnjfJZWd5wgAEieqfPUJCEHd3KavZ47kUkR4-Gg@mail.gmail.com>

On Fri, 2018-06-01 at 10:21 -0700, Andre McCurdy wrote:
> On Fri, Jun 1, 2018 at 7:58 AM, Mark Hatle <mark.hatle@windriver.com>
> wrote:
> > 
> > On 5/31/18 6:10 PM, Andre McCurdy wrote:
> > > 
> > > The Quark machine was EOL'ed at the end of 2017 and all support
> > > for
> > > it has now been removed from meta-intel. Drop the associated
> > > tuning
> > > file from oe-core.
> > I would rather this remain.  There are still a lot of people using
> > the quark
> > based boards as hobbyists... there is little effort to maintain it
> > for now.
> > 
> > (we still have support for ARMv4 for instance, which hasn't really
> > been used in
> > new designs in a while..)
> Is there ever a case when we would drop old tuning files? Or should
> they live on forever?
> 
> We dropped GPLv2 recipes from oe-core on the grounds that they are
> old, unmaintained and untested. ARMv4 CPU tuning files meet those
> criteria too.

We removed the GPLv2 recipes as they created a false sense of security
for people and a message needed to be sent out about them. They were a
maintenance problem.

These tune files aren't really causing a problem right now, from a
maintenance or security perspective.

Yes, we should remove things which are stale/obsolete and not useful
but I think people are using this file and its not causing a problem.

Cheers,

Richard


      parent reply	other threads:[~2018-06-01 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 23:10 [PATCH] tune-i586-nlp.inc: drop tuning file for Intel Quark/X1000 CPU Andre McCurdy
2018-06-01  2:33 ` Trevor Woerner
2018-06-01 14:58 ` Mark Hatle
2018-06-01 17:21   ` Andre McCurdy
2018-06-01 20:12     ` Mark Hatle
2018-06-01 22:45     ` Richard Purdie [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=1527893104.19847.8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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