> -----Original Message-----
> From: Dmytriyenko, Denys
> Sent: Friday, March 29, 2013 12:12 PM
> To: Maupin, Chase
> Cc: [email protected]
> Subject: Re: [meta-arago] [PATCH 1/4] omapconf: add omapconf
> utility to assist testing and debug
> 
> On Fri, Mar 29, 2013 at 01:06:57PM -0400, Maupin, Chase wrote:
> > > -----Original Message-----
> > > From: Dmytriyenko, Denys
> > > Sent: Friday, March 29, 2013 12:01 PM
> > > To: Maupin, Chase
> > > Cc: [email protected]
> > > Subject: Re: [meta-arago] [PATCH 1/4] omapconf: add omapconf
> > > utility to assist testing and debug
> > >
> > > On Fri, Mar 29, 2013 at 08:50:30AM -0500, Chase Maupin wrote:
> > > > * The omapconf utility gives useful information about the
> > > >   state of the OMAP device and can be used in debug and
> > > testing.
> > > >
> > > > Signed-off-by: Chase Maupin <[email protected]>
> > > > ---
> > > >  .../recipes-devtools/omapconf/omapconf_git.bb      |   25
> > > ++++++++++++++++++++
> > > >  1 files changed, 25 insertions(+), 0 deletions(-)
> > > >  create mode 100644 meta-arago-extras/recipes-
> > > devtools/omapconf/omapconf_git.bb
> > > >
> > > > diff --git a/meta-arago-extras/recipes-
> > > devtools/omapconf/omapconf_git.bb b/meta-arago-
> extras/recipes-
> > > devtools/omapconf/omapconf_git.bb
> > > > new file mode 100644
> > > > index 0000000..9fcd88d
> > > > --- /dev/null
> > > > +++ b/meta-arago-extras/recipes-
> > > devtools/omapconf/omapconf_git.bb
> > > > @@ -0,0 +1,25 @@
> > > > +DESCRIPTION = "Diagnostic tool for TI OMAP processors"
> > > > +HOMEPAGE = "https://github.com/omapconf/omapconf";
> > > > +
> > > > +LICENSE = "GPLv2 BSD"
> > > > +LIC_FILES_CHKSUM =
> > > "file://LICENSE;md5=205c83c4e2242a765acb923fc766e914"
> > > > +
> > > > +PV = "1.66"
> > > > +PR = "r0"
> > > > +
> > > > +COMPATIBLE_MACHINE = "omap-a15"
> > >
> > > Is it compatible with omap4? I guess not omap3 though :)
> >
> > Correct.  Since it supports OMAP4 as well I went ahead and left
> it at
> > omap-a15.  OMAP3 wasn't listed as I recall.
> 
> I'm confused. Shouldn't it be omap-a15|omap4?

I didn't notice the pandaboard so I thought there wasn't an existing omap4.  My 
logic was that when/if omap4 was added it would go into the omap-a15 
SOC_FAMILY.  I'll send an update.

> 
> 
> > > > +
> > > > +BRANCH ?= "master"
> > > > +SRCREV = "418b94bde60dbd3f85a0afb6e4d2a808cfb104cd"
> > > > +
> > > > +SRC_URI =
> > >
> "git://github.com/omapconf/omapconf.git;protocol=git;branch=${BRA
> > > NCH}"
> > > > +
> > > > +S = "${WORKDIR}/git"
> > > > +
> > > > +do_compile () {
> > > > +    oe_runmake CROSS_COMPILE=${TARGET_PREFIX} install
> > > > +}
> > > > +
> > > > +do_install () {
> > > > +    oe_runmake DESTDIR=${D}${bindir} install
> > > > +}
> > > > --
> > > > 1.7.0.4
> > > >
> > > > _______________________________________________
> > > > meta-arago mailing list
> > > > [email protected]
> > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-
> arago
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Reply via email to