From: Denys Dmytriyenko <denis@denix.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Denys Dmytriyenko <denys@ti.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Add more tunes for new ARM processors Cortex-A15 and Cortex-A7
Date: Fri, 19 Oct 2012 12:56:16 -0400 [thread overview]
Message-ID: <20121019165616.GA27336@denix.org> (raw)
In-Reply-To: <20121019084432.GH3087@jama.jama.net>
On Fri, Oct 19, 2012 at 10:44:32AM +0200, Martin Jansa wrote:
> On Thu, Oct 18, 2012 at 06:51:56PM -0400, Denys Dmytriyenko wrote:
> > From: Denys Dmytriyenko <denys@ti.com>
> >
> > The patchset adds 2 more standard tune files for the new ARM MPCore (multicore)
> > processors Cortex-A15 and Cortex-A7, as per:
> >
> > http://www.arm.com/products/processors/cortex-a/cortex-a15.php
> > http://www.arm.com/products/processors/cortex-a/cortex-a7.php
>
> Please check this patchset
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-October/030759.html
Yes, I've seen that patchset. Unfortunately it's still in the queue and is
going through implementation iterations. Once it gets into OE-Core, I'd be
happy to update my tune files with the corresponding ARMPKGARCH and
DEFAULTTUNE changes. But I don't think that tune rework patchset should block
new tune files, as they don't break anything and adhere to the existing
framework. Thanks.
--
Denys
> > Denys Dmytriyenko (2):
> > tune-cortexa15: add tunes for ARM Cortex-A15
> > tune-cortexa7: add tunes for ARM Cortex-A7
> >
> > meta/conf/machine/include/tune-cortexa15.inc | 24 ++++++++++++++++++++++++
> > meta/conf/machine/include/tune-cortexa7.inc | 24 ++++++++++++++++++++++++
> > 2 files changed, 48 insertions(+)
> > create mode 100644 meta/conf/machine/include/tune-cortexa15.inc
> > create mode 100644 meta/conf/machine/include/tune-cortexa7.inc
> >
> > --
> > 1.7.12.3
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2012-10-19 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 22:51 [PATCH 0/2] Add more tunes for new ARM processors Cortex-A15 and Cortex-A7 Denys Dmytriyenko
2012-10-18 22:51 ` [PATCH 1/2] tune-cortexa15: add tunes for ARM Cortex-A15 Denys Dmytriyenko
2012-10-18 22:51 ` [PATCH 2/2] tune-cortexa7: add tunes for ARM Cortex-A7 Denys Dmytriyenko
2012-10-19 8:44 ` [PATCH 0/2] Add more tunes for new ARM processors Cortex-A15 and Cortex-A7 Martin Jansa
2012-10-19 16:56 ` Denys Dmytriyenko [this message]
2012-10-19 19:38 ` Martin Jansa
2012-10-19 22:36 ` Richard Purdie
2012-10-19 23:20 ` Martin Jansa
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=20121019165616.GA27336@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=martin.jansa@gmail.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