All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [rocko][PATCH] am65xx-evm: Add am65xx specific soc, boards and cores configuration
Date: Wed, 22 Aug 2018 16:07:59 -0400	[thread overview]
Message-ID: <20180822200758.GG29422@beryl> (raw)
In-Reply-To: <1534968351-4480-1-git-send-email-sam.nelson@ti.com>

I believe the commit message should be:

am65xx-evm: Add PDK specific soc, boards and cores configuration

Otherwise it's kind of circular and confusing.


On Wed, Aug 22, 2018 at 04:05:51PM -0400, Sam Nelson wrote:
> Specifies the pdk soc names, board names and core names supported
> 
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> ---
>  conf/machine/am65xx-evm.conf | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
> index 08dbc9e..82ee02c 100644
> --- a/conf/machine/am65xx-evm.conf
> +++ b/conf/machine/am65xx-evm.conf
> @@ -25,3 +25,8 @@ WKS_FILE = "sdimage-bootpart.wks"
>  IMAGE_BOOT_FILES = "u-boot.img"
>  
>  do_image_wic[depends] += "mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot"
> +
> +# Set the list of device targets for ti-pdk class recipes
> +TI_PDK_LIMIT_SOCS = "am65xx"
> +TI_PDK_LIMIT_BOARDS = "am65xx_evm am65xx_idk"
> +TI_PDK_LIMIT_CORES = "mcu1_0 mpu1_0"
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


      reply	other threads:[~2018-08-22 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 20:05 [rocko][PATCH] am65xx-evm: Add am65xx specific soc, boards and cores configuration Sam Nelson
2018-08-22 20:07 ` 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=20180822200758.GG29422@beryl \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=sam.nelson@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.