From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris.Paterson2@renesas.com (Chris Paterson) Date: Wed, 6 Nov 2019 16:19:39 +0000 Subject: [cip-dev] [isar-cip-core PATCH 0/4] Add rzg2m support In-Reply-To: References: <20191106124439.10532-1-Quirin.Gylstorff@siemens.com> Message-ID: To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org Hello, > From: Gylstorff Quirin > Sent: 06 November 2019 14:37 > > > > 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. Yes, at the moment they are painfully hardcoded. I plan to at least have them point to the 'latest' CIP Core. However for your use case, you'll want to test the binaries you just created. I guess we should decide on whether we want to re-use linux-cip-ci for CIP Core testing, or just end up creating a separate version for CIP Core. Linux-cip-ci could easily be modified to support both CIP Linux & Core testing (we could just add another version of submit_tests.sh for CIP Core), and I think this would be easier to maintain down the line. Is this something you'd like to have a go at? I'm happy to do it, but I may struggle to find time in the next few weeks. Kind regards, Chris > > [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