From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform.
Date: Sun, 09 Jan 2011 13:03:18 +0100 [thread overview]
Message-ID: <m38vyup9mh.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20110108181019.GC11726@game.jcrosoft.org> (Jean-Christophe PLAGNIOL-VILLARD's message of "Sat, 8 Jan 2011 19:10:19 +0100")
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> writes:
> a simple link will be enough so the cramfs is the best solution, I think
> so no data duplication and it will be more easy to update and maintain
>
> And we do not have to known the size of the firmware in barebox just the fs
> location so more easy to update barebox
Agreed. For this I have to be able to set an env variable (then
read-only) from within the board code. How do I do it? Or should I write
this code myself?
> I'm working a the fs support for the env with the idea to have a ro part
> but I need more time to finish it.
Yeah, though it seems a pure cramfs is better suited to my needs anyway,
microcode isn't variable.
> for the size increasement it's impact is cover by the non data duplication
> and will be reduce againt with the envfs
Not a factor for me.
--
Krzysztof Halasa
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-01-09 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 14:48 New round of my IXP42x patches Krzysztof Halasa
2011-01-06 15:23 ` [PATCH 1/3] Fix error handling with malloc, memalign etc. Introduce xmemalign() Krzysztof Halasa
2011-01-06 15:25 ` [PATCH 2/3] ARM: support big/little endian switching in "bootX" Krzysztof Halasa
2011-01-06 15:26 ` [PATCH 3/3] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform Krzysztof Halasa
2011-01-06 23:36 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-08 12:16 ` Krzysztof Halasa
2011-01-08 13:55 ` Sascha Hauer
2011-01-08 17:35 ` Krzysztof Halasa
2011-01-08 18:10 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-09 12:03 ` Krzysztof Halasa [this message]
2011-01-08 13:33 ` Krzysztof Halasa
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=m38vyup9mh.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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