From: Jon Mason <jdmason@kudzu.us>
To: Jon Mason <jon.mason@arm.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [meta-zephyr][PATCH 1/6] zephyr-bsp: add support for qemu-cortex-a9
Date: Fri, 7 Oct 2022 10:19:39 -0400 [thread overview]
Message-ID: <Y0A1e6PVWB3N8jC2@kudzu.us> (raw)
In-Reply-To: <20221007141203.16632-1-jon.mason@arm.com>
FYI, the CI for this series can be seen at
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/660400016
On Fri, Oct 07, 2022 at 10:11:58AM -0400, Jon Mason wrote:
> Signed-off-by: Jon Mason <jon.mason@arm.com>
> ---
> .gitlab-ci.yml | 7 +++++++
> ci/qemu-cortex-a9.yml | 10 ++++++++++
> .../conf/machine/qemu-cortex-a9.conf | 20 +++++++++++++++++++
> 3 files changed, 37 insertions(+)
> create mode 100644 ci/qemu-cortex-a9.yml
> create mode 100644 meta-zephyr-bsp/conf/machine/qemu-cortex-a9.conf
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 5752254..031b5c5 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -90,6 +90,13 @@ qemu-cortex-a53:
> - TOOLCHAIN: [default, zephyr-toolchain]
> TESTING: testimage
>
> +qemu-cortex-a9:
> + extends: .build
> + parallel:
> + matrix:
> + - TOOLCHAIN: [default, zephyr-toolchain]
> + TESTING: testimage
> +
> qemu-cortex-m0:
> extends: .build
> parallel:
> diff --git a/ci/qemu-cortex-a9.yml b/ci/qemu-cortex-a9.yml
> new file mode 100644
> index 0000000..cc44730
> --- /dev/null
> +++ b/ci/qemu-cortex-a9.yml
> @@ -0,0 +1,10 @@
> +header:
> + version: 11
> + includes:
> + - ci/base.yml
> +
> +local_conf_header:
> + failing_tests: |
> + ZEPHYRTESTS:remove = "common queue"
> +
> +machine: qemu-cortex-a9
> diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-a9.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-a9.conf
> new file mode 100644
> index 0000000..9dfee42
> --- /dev/null
> +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-a9.conf
> @@ -0,0 +1,20 @@
> +#@TYPE: Machine
> +#@NAME: qemu-cortex-a9
> +#@DESCRIPTION: Machine for Zephyr BOARD qemu_cortex_a9
> +
> +DEFAULTTUNE ?= "cortexa9"
> +require conf/machine/include/qemu.inc
> +require conf/machine/include/arm/armv7a/tune-cortexa9.inc
> +
> +TCLIBC = "newlib"
> +
> +# For runqemu
> +QB_SYSTEM_NAME = "qemu-system-arm"
> +QB_MACHINE = "-machine xilinx-zynq-a9"
> +QB_CPU = "-cpu cortex-a9"
> +QB_GRAPHICS = "-nographic -vga none"
> +QB_OPT_APPEND = "-icount shift=3,align=off,sleep=off -rtc clock=vm"
> +
> +# Zephyr RTOS settings
> +ZEPHYR_INHERIT_CLASSES += "zephyr-qemuboot"
> +ARCH:qemu-cortex-a9 = "arm"
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2022-10-07 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:11 [meta-zephyr][PATCH 1/6] zephyr-bsp: add support for qemu-cortex-a9 Jon Mason
2022-10-07 14:11 ` [meta-zephyr][PATCH 2/6] zephyr-bsp: add support for mps2-an385 Jon Mason
2022-10-07 14:12 ` [meta-zephyr][PATCH 3/6] zephyr-bsp: add support for mps2-an521 Jon Mason
2022-10-07 14:12 ` [meta-zephyr][PATCH 4/6] zephyr-bsp: add support for mps3-an547 Jon Mason
2022-10-07 14:12 ` [meta-zephyr][PATCH 5/6] zephyr-bsp: add support for v2m-musca-b1 Jon Mason
2022-10-07 14:12 ` [meta-zephyr][PATCH 6/6] zephyr-bsp: add support for v2m-musca-s1 Jon Mason
2022-10-07 14:19 ` Jon Mason [this message]
2022-10-11 3:59 ` [yocto] [meta-zephyr][PATCH 1/6] zephyr-bsp: add support for qemu-cortex-a9 Saini, Naveen Kumar
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=Y0A1e6PVWB3N8jC2@kudzu.us \
--to=jdmason@kudzu.us \
--cc=jon.mason@arm.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