From: quirin.gylstorff@siemens.com (Gylstorff Quirin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [isar-cip-core PATCH 0/4] Add rzg2m support
Date: Wed, 6 Nov 2019 15:37:14 +0100 [thread overview]
Message-ID: <c3dbc38d-c82c-665a-97b5-021921672d83@siemens.com> (raw)
In-Reply-To: <ed9a727a-219c-d991-01d7-09fdf24b7945@siemens.com>
On 11/6/19 3:12 PM, Jan Kiszka wrote:
> Nice! Beyond building and actually deploying this, what else would be
> missing to hook up the result with a board in the lab?
We would need to change the configuration of the LAVA jobs in [1] to
use the tarballs generated by the build.
[1]:
https://gitlab.com/cip-project/cip-testing/linux-cip-ci/blob/next/lava_templates/
From what I see the actions use a hardcoded rootfs url to boot via nfs.
We could use the same template mechanism from Chris for dtb and Kernel
for the rootfs.
Kind regards,
Quirin
next prev parent reply other threads:[~2019-11-06 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:44 [cip-dev] [isar-cip-core PATCH 0/4] Add rzg2m support Q. Gylstorff
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 1/4] kas: Increase Isar version Q. Gylstorff
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 2/4] classes: add wic-targz-img.bbclass Q. Gylstorff
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support Q. Gylstorff
2019-11-06 15:38 ` Chris Paterson
2019-11-06 15:53 ` Gylstorff Quirin
2019-11-07 2:29 ` kazuhiro3.hayashi at toshiba.co.jp
2019-11-07 15:53 ` Gylstorff Quirin
2019-11-08 21:29 ` Pavel Machek
2019-11-11 6:18 ` kazuhiro3.hayashi at toshiba.co.jp
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 4/4] ci: add hihope-rzg2m to ci chain Q. Gylstorff
2019-11-06 15:43 ` Chris Paterson
2019-11-07 16:39 ` [cip-dev] [isar-cip-core PATCH v2 0/4] Add rzg2m support Q. Gylstorff
2019-11-22 7:22 ` Jan Kiszka
2019-11-07 16:39 ` [cip-dev] [isar-cip-core PATCH v2 1/4] kas: Increase Isar version Q. Gylstorff
2019-11-07 16:39 ` [cip-dev] [isar-cip-core PATCH v2 2/4] classes: add wic-targz-img.bbclass Q. Gylstorff
2019-11-07 16:39 ` [cip-dev] [isar-cip-core PATCH v2 3/4] hihope-rzg2m: Add board support Q. Gylstorff
2019-11-07 16:39 ` [cip-dev] [isar-cip-core PATCH v2 4/4] ci: add hihope-rzg2m to ci chain Q. Gylstorff
2019-11-06 14:12 ` [cip-dev] [isar-cip-core PATCH 0/4] Add rzg2m support Jan Kiszka
2019-11-06 14:37 ` Gylstorff Quirin [this message]
2019-11-06 16:19 ` Chris Paterson
2019-11-08 12:57 ` Gylstorff Quirin
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=c3dbc38d-c82c-665a-97b5-021921672d83@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=cip-dev@lists.cip-project.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 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.