Hi Randy,
On Mon, Dec 4, 2023 at 2:39 PM Randy Li <ayaka@xxxxxxxxxxx> wrote:
HelloI guess it started with that we didn't want to download both one Linux
I wonder why Optee OS would use a linux target toolchains but not a bare
metal target(none os)?
and one bare metal toolchain. We need both AArch32 and AArch64
versions so it doubles up.
gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-gccSurely you can define a .h file in a way that you can include it in
-dM -E - < /dev/null|grep linux
#define __linux 1
#define __gnu_linux__ 1
#define linux 1
#define __linux__ 1
That makes hard to share a header files between Linux kernel and Optee.
We like to pass some structure in SHM, but optee don't have all those
Linux types likes <linux/types.h>.
both environments. We try to stick to ISO C.
If optee didn't choose the toolchains for the Linux, we could easilyFeel free to do so.
decide which part would use for Client Agent(Linux kernel) side or TEE
OS side.
Why we don't use bare metal toolchains ?
Cheers,
Jens