--- zzzz-none-000/linux-4.4.60/lib/Kconfig 2017-04-08 07:53:53.000000000 +0000 +++ jet-2400-727/linux-4.4.60/lib/Kconfig 2021-03-17 14:36:41.000000000 +0000 @@ -218,29 +218,38 @@ tristate config ZLIB_INFLATE - tristate + tristate "ZLIB inflate support" config ZLIB_DEFLATE - tristate + tristate "ZLIB deflate support" select BITREVERSE config LZO_COMPRESS - tristate + tristate "LZO compress support" config LZO_DECOMPRESS - tristate + tristate "LZO decompress support" config LZ4_COMPRESS - tristate + tristate "LZ4 compress support" config LZ4HC_COMPRESS - tristate + tristate "LZ4HC compress support" config LZ4_DECOMPRESS - tristate + tristate "LZ4 decompress support" source "lib/xz/Kconfig" +config LZMA_COMPRESS + tristate + +config LZMA_DECOMPRESS + tristate + +config RLE_DECOMPRESS + tristate + # # These all provide a common interface (hence the apparent duplication with # ZLIB_INFLATE; DECOMPRESS_GZIP is just a wrapper.) @@ -334,16 +343,16 @@ # Textsearch support is select'ed if needed # config TEXTSEARCH - bool + boolean "Textsearch support" config TEXTSEARCH_KMP - tristate + tristate "Textsearch KMP" config TEXTSEARCH_BM - tristate + tristate "Textsearch BM" config TEXTSEARCH_FSM - tristate + tristate "Textsearch FSM" config BTREE bool @@ -531,4 +540,13 @@ config ARCH_HAS_MMIO_FLUSH bool +config QMI_ENCDEC + bool "QMI Encode/Decode Library" + help + Library to encode & decode QMI messages from within + the kernel. The kernel drivers encode the C structure into + QMI message wire format and then send it over a transport. + The kernel drivers receive the QMI message over a transport + and then decode it into a C structure. + endmenu