Hi Philippe, On Tue, Jul 6, 2021 at 3:41 PM Philippe Mathieu-Daudé <phi...@redhat.com> wrote: > > Hi Bin, > > On 7/6/21 6:31 AM, Bin Meng wrote: > > Update the QEMU shipped u-boot.e500 image built from U-Boot mainline > > v2021.07 release, which added eTSEC support to the QEMU ppce500 target, > > via the following U-Boot series: > > > > http://patchwork.ozlabs.org/project/uboot/list/?series=233875&state=* > > > > The cross-compilation toolchain used to build the U-Boot image is: > > https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/10.1.0/x86_64-gcc-10.1.0-nolibc-powerpc-linux.tar.xz > > Ideally the process to update a firmware blob is (*): > > - Add a CI job (as you did for .gitlab-ci.d/opensbi.yml) > - Commit the submodule new hash including "git shortlog current..new" > in description > - Run the CI, download the almost-reproducible blob > - Test the blob locally > - Amend to the previous commit the CI blob
Thanks for the guideline! > > Since soft freeze is in 1 week, you might won't have enough time > to add a CI job, so this current patch is acceptable, but please > include the "git shortlog current..new" output. I did consider including the shotlogs here, just like what I did for OpenSBI update. But I am afraid it is a toooo long list because unlike OpenSBI U-Boot is a very active community. Hence I chose not to mention it in the commit message. > > Regards, > > Phil. > > (*) Yes we should document this somewhere. Wiki or docs? Either should be okay. If we put in the docs, we should probably collect some other development processes (e.g.: submitting patches) and put there, like what is done in the Linux kernel. Regards, Bin
