From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org, Fargier Sylvain <sylvain.fargier@somfy.com>
Subject: Re: [PATCH 1/2 v2] filetype: add Binary PacKage BPK type
Date: Tue, 24 Sep 2013 11:37:18 +0200 [thread overview]
Message-ID: <20130924093718.GE30088@pengutronix.de> (raw)
In-Reply-To: <20130924092323.GI31585@ns203013.ovh.net>
On Tue, Sep 24, 2013 at 11:23:23AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 09:34 Tue 24 Sep , Sascha Hauer wrote:
> > On Sat, Sep 21, 2013 at 04:54:15PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > > Signed-off-by: Fargier Sylvain <sylvain.fargier@somfy.com>
> > > ---
> > > common/filetype.c | 3 +++
> > > include/filetype.h | 1 +
> > > 2 files changed, 4 insertions(+)
> > >
> > > diff --git a/common/filetype.c b/common/filetype.c
> > > index 59ea25a..ef4452d 100644
> > > --- a/common/filetype.c
> > > +++ b/common/filetype.c
> > > @@ -51,6 +51,7 @@ static const struct filetype_str filetype_str[] = {
> > > [filetype_png] = { "PNG image", "png" },
> > > [filetype_ext] = { "ext filesystem", "ext" },
> > > [filetype_gpt] = { "GUID Partition Table", "gpt" },
> > > + [filetype_bpk] = { "Binary PacKage", "bpk" },
> >
> > Can we have "Somfy Binary PacKage" here? As this file format is rather
> > exoctic I want to make sure we still know what this is in a few years.
> > Was the CamelCase 'PacKage' intended?
> We drop the Somfy to make it more generic and everyone can use it
> as everything is published
In this case it might be useful to have some pointers *why* someone
should use it. To me it looks like a custom cpio format. What's the
advantage of using this instead of cpio or even uImage?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-09-24 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 14:54 Jean-Christophe PLAGNIOL-VILLARD
2013-09-21 14:54 ` [PATCH 2/2 v2] fs: add BPKFS support Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 7:32 ` Sascha Hauer
2013-09-24 9:24 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 9:33 ` Sascha Hauer
2013-09-24 12:44 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 15:28 ` Sascha Hauer
2013-09-24 16:30 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 7:34 ` [PATCH 1/2 v2] filetype: add Binary PacKage BPK type Sascha Hauer
2013-09-24 9:23 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 9:37 ` Sascha Hauer [this message]
2013-09-24 16:38 ` Jean-Christophe PLAGNIOL-VILLARD
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=20130924093718.GE30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
--cc=sylvain.fargier@somfy.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