All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
To: Wojciech Nizinski <wojciech.nizinski@grinn-global.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] board/freescale/common/imx: imx8-bootloader-prepare: enable error checking
Date: Mon, 5 Feb 2024 17:53:00 +0100	[thread overview]
Message-ID: <506452af-5722-41d3-a5f2-2a9eed0d4263@armadeus.com> (raw)
In-Reply-To: <20230914165046.3687491-1-wojciech.nizinski@grinn-global.com>

Hi Wojciech, All,

I tested your patch and it does work. I have some comments though, see 
below...

On 9/14/23 18:50, Wojciech Nizinski wrote:
> Run script with 'errexit' bash option to detect any errors from
> subcommands.
> 
> It will fix situation where 'ddr_fw.bin' was missing but successfull
> build created broken boot image. Post image script report this by:
> 
> cat: /home/user/buildroot/output/images/ddr_fw.bin: No such file or
> directory
> 
> and build finish with success.
> 
> Signed-off-by: Wojciech Nizinski <wojciech.nizinski@grinn-global.com>
> ---
>   board/freescale/common/imx/imx8-bootloader-prepare.sh | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/board/freescale/common/imx/imx8-bootloader-prepare.sh b/board/freescale/common/imx/imx8-bootloader-prepare.sh
> index 7ebf15b6ff..8d44e588c5 100755
> --- a/board/freescale/common/imx/imx8-bootloader-prepare.sh
> +++ b/board/freescale/common/imx/imx8-bootloader-prepare.sh
> @@ -73,4 +73,5 @@ main ()
>   	exit $?
>   }
>   
> +set -o errexit

For consistency, maybe you should use 'set -e' here. (utils/docker-run 
is the only script that uses '+set -o errexit')

Also, the only way (I am thinking of) to not have the ddr_fw.bin file is 
if the user didn't select the firmware-imx package. Maybe, the script 
should produces an hint to the user about how to get that ddr_fw bin file?

"ddr_fw file not found: did you select firmware-imx package?"

Regards,

>   main $@

-- 
Sébastien Szymanski, Armadeus Systems
Software engineer

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-05 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 16:50 [Buildroot] [PATCH 1/1] board/freescale/common/imx: imx8-bootloader-prepare: enable error checking Wojciech Nizinski
2024-02-05 16:53 ` Sébastien Szymanski [this message]
2024-04-03 21:08 ` Thomas Petazzoni via buildroot
2024-05-02  7:50   ` Peter Korsgaard

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=506452af-5722-41d3-a5f2-2a9eed0d4263@armadeus.com \
    --to=sebastien.szymanski@armadeus.com \
    --cc=buildroot@buildroot.org \
    --cc=wojciech.nizinski@grinn-global.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 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.