From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Xuanhao Shi <X15000177@gmail.com>,
buildroot@buildroot.org, Romain Naour <romain.naour@smile.fr>,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
linux-amarula@amarulasolutions.com,
Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [Buildroot] [RFC PATCH 1/2] support/scripts/genimage.sh: support creating a bmap image
Date: Fri, 31 May 2024 11:47:30 +0200 [thread overview]
Message-ID: <20240531114730.61f9f0fb@windsurf> (raw)
In-Reply-To: <ZkzdeFeoYMkyGv7w@landeda>
On Tue, 21 May 2024 19:44:24 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> I tried a bit earlier, and the genimage file is indeed sparse, but I
> could not find a tool that would report the list of holes/non-holes in a
> file, and their offset, e.g. something like:
>
> size offset
> non-hole 2MiB @0
> hole 1MiB @2MiB
> non-hole 16MiB @3MiB
> and so on...
$ pip3 install sparseutils
$ truncate -s 512M file.img
$ sparsemap file.img
HOLE 536870912
Seems like it's what we're looking for :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-31 9:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 9:53 [Buildroot] [RFC PATCH 0/2] Add support to genimage.sh for creating a bmap image Dario Binacchi
2024-04-21 9:53 ` [Buildroot] [RFC PATCH 1/2] support/scripts/genimage.sh: support " Dario Binacchi
2024-04-23 11:33 ` Gero Schwäricke via buildroot
2024-04-23 12:55 ` Quentin Schulz via buildroot
2024-04-24 7:50 ` Gero Schwäricke via buildroot
2024-04-24 8:06 ` Gero Schwäricke via buildroot
2024-05-10 19:54 ` Thomas Petazzoni via buildroot
2024-05-10 20:17 ` Michael Nazzareno Trimarchi
2024-05-21 5:25 ` Yann E. MORIN
2024-05-21 9:28 ` Michael Nazzareno Trimarchi
2024-05-21 17:44 ` Yann E. MORIN
2024-05-22 15:19 ` Gero Schwäricke via buildroot
2024-05-31 9:47 ` Thomas Petazzoni via buildroot [this message]
2024-05-31 9:44 ` Thomas Petazzoni via buildroot
2024-05-20 8:05 ` Dario Binacchi
2024-05-20 9:23 ` Thomas Petazzoni via buildroot
2024-05-21 15:06 ` Dario Binacchi
2024-05-21 20:36 ` Yann E. MORIN
2024-05-22 15:59 ` Gero Schwäricke via buildroot
2024-07-15 14:05 ` Thomas Petazzoni via buildroot
2024-07-15 14:23 ` Arnout Vandecappelle via buildroot
2024-07-15 14:27 ` Thomas Petazzoni via buildroot
2024-07-16 6:16 ` Dario Binacchi
2024-08-27 18:55 ` Peter Korsgaard
2024-08-28 13:42 ` Thomas Petazzoni via buildroot
2024-08-28 13:58 ` Peter Korsgaard
2024-08-29 21:44 ` Thomas Petazzoni via buildroot
2024-08-30 7:14 ` Peter Korsgaard
2024-08-30 15:29 ` Thomas Petazzoni via buildroot
2024-08-30 15:32 ` Michael Nazzareno Trimarchi
2024-08-31 13:28 ` Peter Korsgaard
2024-08-31 13:20 ` Peter Korsgaard
2024-04-21 9:53 ` [Buildroot] [RFC PATCH 2/2] configs/ti_am62x_sk_defconfig: create the " Dario Binacchi
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=20240531114730.61f9f0fb@windsurf \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=gadiyar@ti.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.