Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx> writes: >> +#define BAREBOX_START 0x00000 >> +#define BAREBOX_LENGTH 0x34000 >> +#define NPE_A_START (BAREBOX_START + BAREBOX_LENGTH) >> +#define NPE_A_LENGTH 0x05000 >> +#define NPE_B_START (NPE_A_START + NPE_A_LENGTH) >> +#define NPE_B_LENGTH 0x03000 >> +#define NPE_C_START (NPE_B_START + NPE_B_LENGTH) >> +#define NPE_C_LENGTH 0x04000 >> +#define NPE_ENV0_START (NPE_C_START + NPE_C_LENGTH) >> +#define NPE_ENV0_LENGTH 0x20000 > I prefer we use a fs to store it so we can share it Linux > with a cramfs at least I wonder... how do I create an read-only environment variable in the board code? The variable should be created before env0 is mounted, but shouldn't be destroyed by mounting env0. I'm thinking of some BAREBOX_PARTITIONS="0x34000@0(barebox),0xC000(barebox-cramfs)". It must be able to survive saveenv followed by a barebox update (which may change the cramfs address and size, i.e. the value saved in env0 must be discarded). -- Krzysztof Halasa _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
