All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH] arm-benchmarks: port benchmarks from old arago
Date: Tue, 31 Jan 2012 16:46:27 -0500	[thread overview]
Message-ID: <20120131214627.GG5169@denix.org> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1010BFA3D5D@DLEE12.ent.ti.com>

On Tue, Jan 31, 2012 at 08:32:57PM +0000, Maupin, Chase wrote:
> 
> > -----Original Message-----
> > From: Denys Dmytriyenko [mailto:denis@denix.org]
> > Sent: Tuesday, January 31, 2012 2:26 PM
> > To: Maupin, Chase
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] [PATCH] arm-benchmarks: port benchmarks
> > from old arago
> > 
> > On Tue, Jan 31, 2012 at 02:03:52PM -0600, Chase Maupin wrote:
> > > * Port the am-benchmarks from the original arago overlay to
> > >   meta-arago
> > > * Change the name to arm-benchmarks
> > > * Modify the recipe for oe-core changes
> > > * Updated the SRCREV to pickup licensing file
> > >
> > > Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
> > > ---
> > >  .../arm-benchmarks/arm-benchmarks_1.3.bb           |   24
> > ++++++++++++++++++++
> > >  1 files changed, 24 insertions(+), 0 deletions(-)
> > >  create mode 100644 meta-arago-extras/recipes-core/arm-
> > benchmarks/arm-benchmarks_1.3.bb
> > 
> > There is a whole set of benchmarks in meta-oe/recipes-benchmark/,
> > so should we
> > use the same path instead of recipes-core?
> 
> I was intending recipes-core to be the recipes that the various SDKs will 
> share.  Maybe my view was too SDK centric, so I'm OK with changing this.  I 
> just didn't want to get to:
> 
> Recipes-benchmark/arm-benchmarks
> Recipes-settigns/am-sysinfo
> Recipes-matrix/matrix

The idea is to group recipes by functionality - i.e. benchmarks, connectivity, 
devtools, multimedia, graphics etc. There are, of course, core and support 
directories, which are more loosely defined :)

So, I'd first look at existing directories in other layers and see if there's 
good fit, if not then resort to core or support. Either way it should be easy 
to move later, if needed.

-- 
Denys


> Etc.  But since recipes-benchmark is already used somewhere else I'll make 
> this change and resubmit.
> 
> > 
> > --
> > Denys
> > 
> > > diff --git a/meta-arago-extras/recipes-core/arm-benchmarks/arm-
> > benchmarks_1.3.bb b/meta-arago-extras/recipes-core/arm-
> > benchmarks/arm-benchmarks_1.3.bb
> > > new file mode 100644
> > > index 0000000..71f5eb8
> > > --- /dev/null
> > > +++ b/meta-arago-extras/recipes-core/arm-benchmarks/arm-
> > benchmarks_1.3.bb
> > > @@ -0,0 +1,24 @@
> > > +DESCRIPTION = "ARM Benchmarks"
> > > +HOMEPAGE = "https://gforge.ti.com/gf/project/am_benchmarks/"
> > > +LICENSE = "BSD"
> > > +LIC_FILES_CHKSUM =
> > "file://COPYING;md5=7aefb5e1cffc7b6a3ef18b803f957922"
> > > +SECTION = "system"
> > > +
> > > +SRCREV = "76"
> > > +PR = "r0+svnr${SRCPV}"
> > > +
> > > +SRC_URI =
> > "svn://gforge.ti.com/svn/am_benchmarks/;module=trunk;proto=https;us
> > er=anonymous;pswd=''"
> > > +
> > > +S = "${WORKDIR}/trunk"
> > > +
> > > +do_compile() {
> > > +	export CROSS_COMPILE=${TARGET_PREFIX}
> > > +	export ARCH=${TUNE_PKGARCH}
> > > +	# build the release version
> > > +	make release
> > > +}
> > > +
> > > +do_install() {
> > > +	export ARCH=${TUNE_PKGARCH}
> > > +	make DESTDIR=${D} install
> > > +}
> > > --
> > > 1.7.0.4
> > >
> > > _______________________________________________
> > > meta-arago mailing list
> > > meta-arago@arago-project.org
> > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> > >
> 


      reply	other threads:[~2012-01-31 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 20:03 [PATCH] arm-benchmarks: port benchmarks from old arago Chase Maupin
2012-01-31 20:25 ` Denys Dmytriyenko
2012-01-31 20:32   ` Maupin, Chase
2012-01-31 21:46     ` 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=20120131214627.GG5169@denix.org \
    --to=denis@denix.org \
    --cc=chase.maupin@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.