From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 8 Nov 2019 16:59:44 -0500 From: Tom Rini Subject: Re: [U-Boot] Using kernelCI infrastructure for firmware testing Message-ID: <20191108215944.GS19317@bill-the-cat> References: MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RWwYAm6PHzOoZjya" Content-Disposition: inline List-ID: To: Patrick Rudolph Cc: kernelci@groups.io, pietrushnic@gmail.com, u-boot@lists.denx.de, Coreboot --RWwYAm6PHzOoZjya Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 08, 2019 at 10:35:10AM +0100, Patrick Rudolph wrote: > Hi folks, > this is an attempt to improve firmware testing by using the > infrastructure and knowledge of the kernelci community. If you think > this is not the right place, please point me in the right direction. >=20 > I'm a coreboot[1] developer trying to make sure that the master > branch[2] doesn't regress. Currently there's no public firmware > testing, only internal validation suites used by some companies that > lack direct and automated feedback before a commit is actually merged. > As this isn't a coreboot only topic, but applies to all open source > "bios vendors", I added the u-boot project in CC as well. >=20 > For me firmware testing looks pretty similar to kernel testing: > * flash firmware to test > * boot a known good linux kernel > * run tests in userspace and verify hardware/software works as expected >=20 > On the hardware side we have boards in our lab that allow remote power > cycling and firmware flashing. It is attached to self hosted stock > LAVA2018. But as we are firmware engineers, we don't want to deal with > the administration of servers. >=20 > Here are a few questions for you: > * Would it make sense to also cover open source firmware tests on kernelc= i? > * Do you build the linux images yourself? > * Would you accept firmware images generated by a third party? > * Can anybody get an account for the LAVA server to run firmware test? > * What communication channels do you recommend? > * Will there be meetings or conferences to get in contact with the > community to talk about this? >=20 > [1]: https://coreboot.org/ > [2]: https://review.coreboot.org/ Over in U-Boot, yes, we have some test suites that we run on real HW as well as QEMU-based hardware. And historically I've talked with Kevin once or twice about testing a current U-Boot on various easy-to-recover boards rather than just what it shipped with, but things never moved past the talking about it stage. --=20 Tom --RWwYAm6PHzOoZjya Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE6HLbQJwaaH776GM2h/n2NdMddlIFAl3F5VAACgkQh/n2NdMd dlJKARAAouSIf+nHWloJjg2HX3BhVsj04ggjBdmAVgRgRDO2v4MPdOR/leg/kGdx Asifv1b6KH5cKd9OfvgaT3CM5aQoeAzwzQoraKkv4mLxyWQTMCcd9fMj3fxx6mOm Zc59mzOpTCCQmAD8NEctQFRNITClR5NDZbrxk7mRrd+2m1GmCMdR6k4pfgjq3lg8 sEjEmxSfDpoucBZ5+dL/byUZlnbKXO32m8DfozAVjDwOY/3jXAjhYoJuT4PCNIwT wA653/P4uXQjtcp0JC4dim1NR52POL3D52HqOFS22TzWT8zkC0Vjhv/lY9l/xU76 OzcNQH3XZFJlE34dvfk5NiP2A2W+ONtPuuKeoXqFxnkcQnzs0yGqqeb0h47l2P4A yfYWhv5ej2ugv1wY1SnkhMFAfmwHb4IfLT+gjrCkJDq7r5GNQWZnqV8R+t/fSJ8v gmO52K5ObYA7YFa6k6TQoQwsMrhQDMdC7ANHbYUMDanAHO/dUNv6TNdQxGfeMW4R IjtRQrV3wBVgp7c7HB00oqtiiD77LB2GTUPAovNL9908xEjoUMGThClkPf76cC3F uqnhLlYKCqlv99FhSuQpCLUQ+foGVGWilxE9rrBYncl7CFnwlSGRbM+C3Sm+O8wR Q5k544fcQBnrJyMLvuI9zMod1mxxpsuY6QlkTJUh5b4QeF1hNQg= =EuA+ -----END PGP SIGNATURE----- --RWwYAm6PHzOoZjya--