Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
