Re: libfdt: Handle v16 and re-ordered trees for r/w

2007-11-01 Thread Jon Loeliger
So, like, the other day David Gibson mumbled: > Currently all the read/write functions in libfdt require that the > given tree be v17, and further, that the tree has the memory > reservation block, structure block and strings block stored in that > physical order. > > This patch eases these constr

libfdt: Handle v16 and re-ordered trees for r/w

2007-10-31 Thread David Gibson
Currently all the read/write functions in libfdt require that the given tree be v17, and further, that the tree has the memory reservation block, structure block and strings block stored in that physical order. This patch eases these constraints, by making fdt_open_int() reorder the blocks, and/or