CONFIG_CRAMFS_MTD: Support CramFs image directly mapped in physical memory

General informations

The Linux kernel configuration item CONFIG_CRAMFS_MTD:

• prompt: Support CramFs image directly mapped in physical memory
• type: bool
• depends on: ( CONFIG_CRAMFS && CONFIG_CRAMFS <= CONFIG_MTD ) && (! CONFIG_CRAMFS_BLOCKDEV )
• defined in fs/cramfs/Kconfig
• found in Linux kernels: 4.15–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

This option allows the CramFs driver to load data directly from a linear addressed memory range (usually non-volatile memory like flash) instead of going through the block device layer. This saves some memory since no intermediate buffering is necessary.

The location of the CramFs image is determined by a MTD device capable of direct memory mapping e.g. from the 'physmap' map driver or a resulting MTD partition. For example, this would mount the cramfs image stored in the MTD partition named "xip_fs" on the /mnt mountpoint:

mount -t cramfs mtd:xip_fs /mnt

If unsure, say N.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: