Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Alex G." <mr.nuke.me@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: How to assemble FIT images with linux and OPTEE?
Date: Thu, 15 Oct 2020 09:46:32 -0500	[thread overview]
Message-ID: <e7cca6ee-ca65-9d07-354e-070bf8b63614@gmail.com> (raw)

Hi,

I'm trying to write a recipe for a secure boot flow. It would look 
something like this:

	images {
		optee@1 { "path/to/tee.bin" }
		linux@2 { "path/to/zImage" }
		fdt@board { ... }
	}
	configurations {
		secure {
			kernel = "optee@1";
			loadables = "linux@2";
			fdt = "fdt@board";
		}
	}

I've tried to "inherit kernel-fitimage", but soon learned of a couple of 
limitations:
	* images: No way to add an optee binary
	* configurations: No way to add a "loadables"

Secondly, since this approach would use files from several packages, I 
think it would be better to have the recipe separate from the kernel 
build. Bot how would I use files from another recipe? All I could figure 
out was to first put them in ${DEPLOY_DIR_IMAGE}.

What would be the "correct" way to write such a recipe?

Alex

                 reply	other threads:[~2020-10-15 14:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e7cca6ee-ca65-9d07-354e-070bf8b63614@gmail.com \
    --to=mr.nuke.me@gmail.com \
    --cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox