From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] [RFC] tools: fitmount: fuse mount fit images
Date: Tue, 23 Jun 2020 14:16:59 -0400 [thread overview]
Message-ID: <20200623181659.GU27801@bill-the-cat> (raw)
In-Reply-To: <CAG+MFZw1fjhhhP6EYSRhJoR+9dTOLq=u5BtejJP=cStwDezzDw@mail.gmail.com>
On Tue, Jun 23, 2020 at 06:01:38PM +0530, selvamuthukumar v wrote:
> On Mon, Jun 15, 2020 at 11:15 PM Selva Muthukumar
> <v.selvamuthukumar@gmail.com> wrote:
> >
> > Allow mounting of FIT images. If FIT images are used for firmware upgrade
> > from linux, mouting can save space in comparison to using dumpimage.
> >
>
> Any comments on this? Is there any other way to get FIT image
> contents, without extracting it?
Sorry for the delay. For your program, there's a few things such as
missing license header and being able to opt-in as otherwise we add a
new build dependency for everyone.
For getting FIT image contents, the existing dumpimage tool handles
this.
What is missing and would be greatly appreciated is updating some
documentation to include what's described in:
commit 39931f966adaeadd66dc7a905f7dddb93f66bac3
Author: Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>
Date: Thu Jan 15 02:54:42 2015 -0200
dumpimage: fit: extract FIT images
to be much more visible. What's documented there works today but I had
to double check how myself as it's not as visible as it should be.
Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200623/292376ec/attachment.sig>
next prev parent reply other threads:[~2020-06-23 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 17:45 [PATCH] [RFC] tools: fitmount: fuse mount fit images Selva Muthukumar
2020-06-23 12:31 ` selvamuthukumar v
2020-06-23 18:16 ` Tom Rini [this message]
2020-06-24 2:50 ` selvamuthukumar v
2020-06-24 11:55 ` Rasmus Villemoes
2020-06-24 12:47 ` Selva Muthukumar
2020-06-24 18:17 ` Tom Rini
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=20200623181659.GU27801@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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