Searched hist:fd4f6f2a78aeaebb7094c1bb9b30623d18a86e4c (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/cramfs/ |
| H A D | README | diff fd4f6f2a78aeaebb7094c1bb9b30623d18a86e4c Thu Oct 12 01:16:11 CDT 2017 Nicolas Pitre <nicolas.pitre@linaro.org> cramfs: implement uncompressed and arbitrary data block positioning
Two new capabilities are introduced here:
- The ability to store some blocks uncompressed.
- The ability to locate blocks anywhere.
Those capabilities can be used independently, but the combination
opens the possibility for execute-in-place (XIP) of program text segments
that must remain uncompressed, and in the MMU case, must have a specific
alignment. It is even possible to still have the writable data segments
from the same file compressed as they have to be copied into RAM anyway.
This is achieved by giving special meanings to some unused block pointer
bits while remaining compatible with legacy cramfs images.
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Chris Brandt <chris.brandt@renesas.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| H A D | inode.c | diff fd4f6f2a78aeaebb7094c1bb9b30623d18a86e4c Thu Oct 12 01:16:11 CDT 2017 Nicolas Pitre <nicolas.pitre@linaro.org> cramfs: implement uncompressed and arbitrary data block positioning
Two new capabilities are introduced here:
- The ability to store some blocks uncompressed.
- The ability to locate blocks anywhere.
Those capabilities can be used independently, but the combination
opens the possibility for execute-in-place (XIP) of program text segments
that must remain uncompressed, and in the MMU case, must have a specific
alignment. It is even possible to still have the writable data segments
from the same file compressed as they have to be copied into RAM anyway.
This is achieved by giving special meanings to some unused block pointer
bits while remaining compatible with legacy cramfs images.
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Chris Brandt <chris.brandt@renesas.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | cramfs_fs.h | diff fd4f6f2a78aeaebb7094c1bb9b30623d18a86e4c Thu Oct 12 01:16:11 CDT 2017 Nicolas Pitre <nicolas.pitre@linaro.org> cramfs: implement uncompressed and arbitrary data block positioning
Two new capabilities are introduced here:
- The ability to store some blocks uncompressed.
- The ability to locate blocks anywhere.
Those capabilities can be used independently, but the combination
opens the possibility for execute-in-place (XIP) of program text segments
that must remain uncompressed, and in the MMU case, must have a specific
alignment. It is even possible to still have the writable data segments
from the same file compressed as they have to be copied into RAM anyway.
This is achieved by giving special meanings to some unused block pointer
bits while remaining compatible with legacy cramfs images.
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Chris Brandt <chris.brandt@renesas.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|