All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Eatmon <reatmon@ti.com>
To: Andrew Davis <afd@ti.com>, Denys Dmytriyenko <denys@konsulko.com>,
	<meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][dunfell][PATCH 1/2] ti-sci-fw: Allow build to continue without TI_SECURE_DEV_PKG set
Date: Wed, 10 Aug 2022 10:58:48 -0500	[thread overview]
Message-ID: <e01176e5-f142-b877-e8e1-8476a25b9be5@ti.com> (raw)
In-Reply-To: <20220810144708.14171-1-afd@ti.com>



On 8/10/2022 9:47, Andrew Davis wrote:
> If we do not have TI_SECURE_DEV_PKG set then SYSFW generation will fail
> if we are building for the HS platform. When TI_SECURE_DEV_PKG is not
> set we assume the builder is only interested in the GP boards, so fake
> generating the HS SYSFW images. These will be non-functional on HS
> boards, but they would have been just as non-functional if built
> without TI_SECURE_DEV_PKG set.


Have you tested what happens if they do not have it set and build the 
"dummy" files, and then realize their mistake, set the variable and 
build again?  Do the files then build correctly, or does the sstate 
cache prevent them from getting the correct thing without clearing the 
cache and rebuilding everything?




-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS


  parent reply	other threads:[~2022-08-10 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 14:47 [meta-ti][dunfell][PATCH 1/2] ti-sci-fw: Allow build to continue without TI_SECURE_DEV_PKG set Andrew Davis
2022-08-10 14:47 ` [meta-ti][dunfell][PATCH 2/2] conf: machine: am64xx-evm: Make HS-SE the default Andrew Davis
2022-08-10 16:11   ` Denys Dmytriyenko
2022-08-10 16:37     ` Andrew Davis
2022-08-10 15:58 ` Ryan Eatmon [this message]
2022-08-10 16:00   ` [meta-ti][dunfell][PATCH 1/2] ti-sci-fw: Allow build to continue without TI_SECURE_DEV_PKG set Andrew Davis
2022-08-10 16:05     ` Ryan Eatmon
2022-08-10 16:25 ` Andrew Davis
2022-08-12  1:47   ` Andrew Davis

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=e01176e5-f142-b877-e8e1-8476a25b9be5@ti.com \
    --to=reatmon@ti.com \
    --cc=afd@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.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.