summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2017-05-17 03:25:42 -0600
committerTom Rini <trini@konsulko.com>2017-05-22 12:45:32 -0400
commitaed998aa34b22e818b2cd58ca7f2246716f2c3a6 (patch)
treeae02a003bdbba0da36dc3097ffaf8e76bb670848 /README
parent4a37cb50386a8affa2cfc68874ba88664b8ceca2 (diff)
Convert CONFIG_LZMA to Kconfig
This converts the following to Kconfig: CONFIG_LZMA Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
-rw-r--r--README23
1 files changed, 0 insertions, 23 deletions
diff --git a/README b/README
index 98a51dcb80..9d351ec5ad 100644
--- a/README
+++ b/README
@@ -1723,29 +1723,6 @@ The following options need to be configured:
the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
be at least 4MB.
- CONFIG_LZMA
-
- If this option is set, support for lzma compressed
- images is included.
-
- Note: The LZMA algorithm adds between 2 and 4KB of code and it
- requires an amount of dynamic memory that is given by the
- formula:
-
- (1846 + 768 << (lc + lp)) * sizeof(uint16)
-
- Where lc and lp stand for, respectively, Literal context bits
- and Literal pos bits.
-
- This value is upper-bounded by 14MB in the worst case. Anyway,
- for a ~4MB large kernel image, we have lc=3 and lp=0 for a
- total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is
- a very small buffer.
-
- Use the lzmainfo tool to determinate the lc and lp values and
- then calculate the amount of needed dynamic memory (ensuring
- the appropriate CONFIG_SYS_MALLOC_LEN value).
-
CONFIG_LZO
If this option is set, support for LZO compressed images