From: Jon Mason <jdmason@kudzu.us>
To: Khem Raj <raj.khem@gmail.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [PATCH v2 3/4] linux-yocto: Add bbappend for 5.19
Date: Thu, 22 Sep 2022 20:40:52 -0400 [thread overview]
Message-ID: <Yy0AlN5vMSG63Ndd@kudzu.us> (raw)
In-Reply-To: <20220922005409.3378701-3-raj.khem@gmail.com>
On Wed, Sep 21, 2022 at 05:54:08PM -0700, Khem Raj wrote:
> Enable tee and arm-ffa driver on qemuarm/qemuarm64 by default
Per Anton's comment, I don't see why this is necessary for
qemuarm/qemuarm64 by default. Can you explain a little more please?
Aside from this, the series looks fine.
Thanks,
Jon
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> v2: Rebased
>
> meta-arm/recipes-kernel/linux/linux-yocto_5.19%.bbappend | 9 +++++++++
> 1 file changed, 9 insertions(+)
> create mode 100644 meta-arm/recipes-kernel/linux/linux-yocto_5.19%.bbappend
>
> diff --git a/meta-arm/recipes-kernel/linux/linux-yocto_5.19%.bbappend b/meta-arm/recipes-kernel/linux/linux-yocto_5.19%.bbappend
> new file mode 100644
> index 0000000..7dec2f5
> --- /dev/null
> +++ b/meta-arm/recipes-kernel/linux/linux-yocto_5.19%.bbappend
> @@ -0,0 +1,9 @@
> +# enable arm_ffa regardless on 5.19
> +SRC_URI:append:qemuarm = " \
> + file://tee.cfg \
> + file://arm-ffa-transport.cfg \
> +"
> +SRC_URI:append:qemuarm64 = " \
> + file://tee.cfg \
> + file://arm-ffa-transport.cfg \
> +"
> --
> 2.37.3
>
>
next prev parent reply other threads:[~2022-09-23 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 0:54 [PATCH v2 1/4] optee-os: Extend clang pragma fixes to core_mmu_v7.c for 3.18 Khem Raj
2022-09-22 0:54 ` [PATCH v2 2/4] trusted-services: Pin to use gcc Khem Raj
2022-09-22 0:54 ` [PATCH v2 3/4] linux-yocto: Add bbappend for 5.19 Khem Raj
2022-09-23 0:40 ` Jon Mason [this message]
2022-09-23 1:21 ` Khem Raj
2022-09-22 0:54 ` [PATCH v2 4/4] ffa-debugfs-mod: Exclude from world builds Khem Raj
2022-09-23 15:31 ` [PATCH v2 1/4] optee-os: Extend clang pragma fixes to core_mmu_v7.c for 3.18 Jon Mason
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=Yy0AlN5vMSG63Ndd@kudzu.us \
--to=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
--cc=raj.khem@gmail.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.