From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 0/2] Actualize iMX6 targets
Date: Mon, 17 Jan 2022 08:34:06 +0300 [thread overview]
Message-ID: <20220117053408.250503-1-amikan@ilbers.de> (raw)
We are planning to move UBI image prepare test target from SABRE Lite
i.MX6 Development Board to phyBOARD-Mira later on. So adding
phyboard-mira machine and rename nand-ubi-demo machine to more clear
imx6-sabrelite, both covered by CI for now.
---
Changes since v1:
- Rebase on latest next and testsuite updates.
- Set year 2022 in copyrights.
Anton Mikanovich (2):
meta-isar: Rename nand-ubi-demo to imx6-sabrelite
meta-isar: Add phyboard-mira target
meta-isar/conf/local.conf.sample | 5 +++--
.../{nand-ubi-demo.conf => imx6-sabrelite.conf} | 0
meta-isar/conf/machine/phyboard-mira.conf | 13 +++++++++++++
...o-bullseye.conf => imx6-sabrelite-bullseye.conf} | 2 +-
...-demo-buster.conf => imx6-sabrelite-buster.conf} | 2 +-
.../conf/multiconfig/phyboard-mira-bullseye.conf | 13 +++++++++++++
testsuite/build_test/build_test.py | 3 ++-
7 files changed, 33 insertions(+), 5 deletions(-)
rename meta-isar/conf/machine/{nand-ubi-demo.conf => imx6-sabrelite.conf} (100%)
create mode 100644 meta-isar/conf/machine/phyboard-mira.conf
rename meta-isar/conf/multiconfig/{nand-ubi-demo-bullseye.conf => imx6-sabrelite-bullseye.conf} (86%)
rename meta-isar/conf/multiconfig/{nand-ubi-demo-buster.conf => imx6-sabrelite-buster.conf} (88%)
create mode 100644 meta-isar/conf/multiconfig/phyboard-mira-bullseye.conf
--
2.25.1
next reply other threads:[~2022-01-17 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 5:34 Anton Mikanovich [this message]
2022-01-17 5:34 ` [PATCH v2 1/2] meta-isar: Rename nand-ubi-demo to imx6-sabrelite Anton Mikanovich
2022-01-17 5:34 ` [PATCH v2 2/2] meta-isar: Add phyboard-mira target Anton Mikanovich
2022-01-24 8:02 ` [PATCH v2 0/2] Actualize iMX6 targets Anton Mikanovich
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=20220117053408.250503-1-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox