From: "'Shekar, Kasturi' via isar-users" <isar-users@googlegroups.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH] isar-installer: show progress bar during bmaptool copy process
Date: Mon, 10 Mar 2025 05:25:40 +0000 [thread overview]
Message-ID: <SG2PR06MB531137E8BA73B72BE10F96C294D62@SG2PR06MB5311.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <98136ab9-5b75-49c3-8b7b-f6eb9d900245@siemens.com>
-----Original Message-----
From: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com>
Sent: 07 March 2025 16:11
To: Shekar, Kasturi (FT FDS CES LX PBU 2) <kasturi.shekar@siemens.com>; isar-users@googlegroups.com
Subject: Re: [PATCH] isar-installer: show progress bar during bmaptool copy process
On 06.03.25 11:28, 'Kasturi Shekar' via isar-users wrote:
> - Added support for a progress gauge using a named pipe to capture and
> display percentage progress when using `bmaptool`.
> - The progress bar is displayed only when the `bmaptool` version is
> 3.8 or above, as versions prior to 3.8 has some issues with `--psplash-pipe` flag.
Which issues were these? Is there some related upstream or Debian bug?
3.8 means trixie, just to clearify.
Yes, it’s a Debian issue and 3.8 is Trixie.
> - For `bmaptool` versions below 3.8, the image copy process continues
> without a progress bar to maintain compatibility.
> - The gauge uses `dialog --gauge` to dynamically update the progress
> based on output from the `bmaptool` process.
>
> Signed-off-by: Kasturi Shekar <kasturi.shekar@siemens.com>
> ---
> .../files/usr/bin/deploy-image-wic.sh | 44 ++++++++++++++++++-
> 1 file changed, 42 insertions(+), 2 deletions(-)
>
> diff --git
> a/meta-isar/recipes-installer/deploy-image/files/usr/bin/deploy-image-
> wic.sh
> b/meta-isar/recipes-installer/deploy-image/files/usr/bin/deploy-image-
> wic.sh
> index 7f552eee..1265d0cc 100755
> ---
> a/meta-isar/recipes-installer/deploy-image/files/usr/bin/deploy-image-
> wic.sh
> +++ b/meta-isar/recipes-installer/deploy-image/files/usr/bin/deploy-im
> +++ age-wic.sh
> @@ -149,8 +149,48 @@ if ! $installer_unattended; then
> clear
> fi
>
> -if ! bmaptool copy ${bmap_options} "$installer_image_uri" "${installer_target_dev}"; then
> - exit 1
> +# Function to compare version numbers
> +version_gt() {
> + if [ "$(printf '%s\n' "$1" "$2" | sort -V | head -n 1)" != "$1"
> +]; then
This should be possible as well:
version_ge() {
if [ "$(printf '%s\n' "$1"X "$2" | sort -V | head -n 1)" != "$1"X ]; then
> + return 0
> + else
> + return 1
> + fi
> +}
> +
> +# Get bmap-tools version using dpkg-query bmap_version=$(dpkg-query
> +-W -f='${Version}' bmap-tools | awk -F'[~+-]' '{ print $1 }')
> +
> +if version_gt "$bmap_version" "3.8" || [ "$bmap_version" = "3.8" ];
> +then
... and will obsolete the second test.
> + # Create a named pipe for progress communication
> + progress_pipe="/tmp/progress"
> + if ! mkfifo "$progress_pipe"; then
> + echo "Error: Failed to create named pipe $progress_pipe"
> + exit 1
> + fi
> +
> + # Initialize the dialog gauge and update it dynamically
> + (
> + while true; do
> + if read -r line < "$progress_pipe"; then
> + percentage=$(echo "$line" | awk '{ print $2 }')
> + echo "$percentage"
> + fi
> + done
> + ) | dialog --gauge "Flashing image, please wait..." 10 70 0 &
> +
> + # Run bmaptool with psplash for versions greater than or equal to
> + 3.8
The version tests are done above - commenting here is a bit confusing.
> + if ! bmaptool -q copy ${bmap_options} --psplash-pipe="$progress_pipe" "$installer_image_uri" "$installer_target_dev"; then
> + exit 1
> + fi
> +
> + # Clean up the named pipe after completion
> + rm "$progress_pipe"
> +
> +else
> + if ! bmaptool copy ${bmap_options} "$installer_image_uri" "$installer_target_dev"; then
> + exit 1
> + fi
> fi
>
> if ! $installer_unattended; then
Didn't try yet, but I can imagine that it looks nice :)
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/SG2PR06MB531137E8BA73B72BE10F96C294D62%40SG2PR06MB5311.apcprd06.prod.outlook.com.
next prev parent reply other threads:[~2025-03-10 5:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 10:28 'Kasturi Shekar' via isar-users
2025-03-07 10:41 ` 'Jan Kiszka' via isar-users
2025-03-10 5:25 ` 'Shekar, Kasturi' via isar-users [this message]
2025-03-10 5:40 ` 'Shekar, Kasturi' via isar-users
2025-03-10 6:29 ` 'Jan Kiszka' via isar-users
[not found] <KLEL2lkm9BY>
2025-03-14 6:28 ` 'Kasturi Shekar' via isar-users
2025-03-17 5:49 ` 'Kasturi Shekar' via isar-users
2025-03-17 12:22 ` 'Quirin Gylstorff' via isar-users
2025-03-18 5:20 ` 'Kasturi Shekar' via isar-users
2025-03-18 6:05 ` 'Jan Kiszka' via isar-users
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=SG2PR06MB531137E8BA73B72BE10F96C294D62@SG2PR06MB5311.apcprd06.prod.outlook.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kasturi.shekar@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox