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 2/2 v2] fs: add BPKFS support
Date: Tue, 24 Sep 2013 17:28:36 +0200 [thread overview]
Message-ID: <20130924152836.GF30088@pengutronix.de> (raw)
In-Reply-To: <20130924124442.GL31585@ns203013.ovh.net>
On Tue, Sep 24, 2013 at 02:44:42PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 11:33 Tue 24 Sep , Sascha Hauer wrote:
> > On Tue, Sep 24, 2013 at 11:24:50AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > On 09:32 Tue 24 Sep , Sascha Hauer wrote:
> > > > Some typos inside
> > > >
> > > > On Sat, Sep 21, 2013 at 04:54:16PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > > Simple update file format developped for Somfy, tools and library are
> > > >
> > > > s/developped/developed/
> > > >
> > > > > +/*
> > > > > + * Copyright (c) 2013 Jean-Chritstophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > > >
> > > > s/Jean-Chritstophe/Jean-Christophe/
> > >
> > > a tyPo in my own name :(
> > > >
> > > > Otherwise this looks good.
> > >
> > > for some times I was thinking to do the same on uimage
> > >
> > > so we do not need to extract struff from it
> >
> > I have a patch that drops multifile uImage support. It really makes the
> > bootm code more readable.
>
> NO I does use it and in production board
>
> we must have multifile uImage support
That was in response to "I was thinking to do the same on uimage" which
I interpreted in the way that you thought about implementing uimage
support as filesystem which would allow us to remove the multifile
support from bootm without loosing the feature of handling multifile
images.
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 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 14:54 [PATCH 1/2 v2] filetype: add Binary PacKage BPK type 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 [this message]
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
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=20130924152836.GF30088@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