All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Tivy, Robert" <rtivy@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
	"Ring, Chris" <cring@ti.com>
Subject: Re: [PATCH v2] cmem: Adding New recipe for cmem
Date: Thu, 7 Nov 2013 21:03:30 -0500	[thread overview]
Message-ID: <20131108020330.GX4510@edge> (raw)
In-Reply-To: <13514BD7FAEBA745BBD7D8A672905C14573A6C45@DFLE12.ent.ti.com>

On Thu, Nov 07, 2013 at 09:00:08PM -0500, Tivy, Robert wrote:
> Please see one response below...
> 
> Regards,
> 
> - Rob
> 
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Thursday, November 07, 2013 5:53 PM
> > To: Nelson, Sam
> > Cc: Maupin, Chase; meta-arago@arago-project.org; Ring, Chris; Tivy,
> > Robert
> > Subject: Re: [meta-arago] [PATCH v2] cmem: Adding New recipe for cmem
> > 
> > 
> > > > >+}
> > > > >diff --git a/recipes-bsp/cmem/cmem.inc b/recipes-bsp/cmem/cmem.inc
> > > > >new file mode 100644
> > > > >index 0000000..5d17d8e
> > > > >--- /dev/null
> > > > >+++ b/recipes-bsp/cmem/cmem.inc
> > > > >@@ -0,0 +1,12 @@
> > > > >+HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:CMEM"
> > > > >+
> > > > >+LICENSE = "GPLv2"
> > > > >+LIC_FILES_CHKSUM =
> > > > >"file://include/ti/cmem.h;beginline=1;endline=30;md5=b86138d4028fb
> > > > >8310b3b983024edc620"
> > > > >+
> > > > >+COMPATIBLE_MACHINE = "keystone-evm"
> > > >
> > > > As Sidd pointed out is there any reason not to add the other
> > devices like
> > > > omap-a15 as compatible machines?
> > >
> > > [Sam] I am fine with remove the compatible machine. Although this is
> > not
> > > tested with other machines.
> > 
> > So, Chris and Rob should comment on which platforms this version of
> > cmem is
> > supposed to be compatible with, even if it's not tested yet.
> > 
> 
> CMEM is completely architecture-independent.  The only HW it touches is 
> memory, and the memory it touches is specified by the user/system 
> integrator.

Thanks. Then it doesn't make sense to artificially limit it to Keystone only.

-- 
Denys


  reply	other threads:[~2013-11-08  2:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  5:03 [PATCH v2] cmem: Adding New recipe for cmem Sam Nelson
2013-11-07  7:35 ` Maupin, Chase
2013-11-07 11:49   ` Nelson, Sam
2013-11-08  0:33     ` Tivy, Robert
2013-11-08  2:02       ` Denys Dmytriyenko
2013-11-08  1:53     ` Denys Dmytriyenko
2013-11-08  2:00       ` Tivy, Robert
2013-11-08  2:03         ` Denys Dmytriyenko [this message]
2013-11-08  2:04           ` Nelson, Sam
2013-11-08  2:06       ` Nelson, Sam
2013-11-12 21:01       ` Nelson, Sam
2013-11-12 21:20         ` Denys Dmytriyenko
2013-11-20 13:11 ` Maupin, Chase
2013-11-20 15:24   ` Denys Dmytriyenko
2013-11-26 12:56     ` Enrico
2013-11-27 16:55       ` Denys Dmytriyenko
2013-11-28  8:20         ` Enrico

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=20131108020330.GX4510@edge \
    --to=denys@ti.com \
    --cc=cring@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=rtivy@ti.com \
    /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.