summaryrefslogtreecommitdiffstats
path: root/external/pflash/test/files/01-info.ffs
diff options
context:
space:
mode:
authorCyril Bur <cyril.bur@au1.ibm.com>2018-03-15 16:58:24 +1100
committerStewart Smith <stewart@linux.ibm.com>2018-04-09 03:45:23 -0500
commit1622957255a66c026d9502219171b0f9e4996b4c (patch)
tree7972a3882ae1803b4405b90eb1ab1be32658663b /external/pflash/test/files/01-info.ffs
parent79316cb6aca6fc79585f4f47c18a37f2eb177780 (diff)
downloadblackbird-skiboot-1622957255a66c026d9502219171b0f9e4996b4c.tar.gz
blackbird-skiboot-1622957255a66c026d9502219171b0f9e4996b4c.zip
libflash/libffs: Allow caller to specifiy header partition
An FFS TOC is comprised of two parts. A small header which has a magic and very minimmal information about the TOC which will be common to all partitions, things like number of patritions, block sizes and the like. Following this small header are a series of entries. Importantly there is always an entry which encompases the TOC its self, this is usually called the 'part' partition. Currently libffs always assumes that the 'part' partition is at zero. While there is always a TOC and zero there doesn't actually have to be. PNORs may have multiple TOCs within them, therefore libffs needs to be flexible enough to allow callers to specify TOCs not at zero. The 'part' partition is otherwise a regular partition which may have flags associated with it. libffs should allow the user to set the flags for the 'part' partition. This patch achieves both by allowing the caller to specify the 'part' partition. The caller can not and libffs will provide a sensible default. Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'external/pflash/test/files/01-info.ffs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud