CONFIG_MTD_BLOCK: Caching block device access to MTD devices

General informations

The Linux kernel configuration item CONFIG_MTD_BLOCK has multiple definitions:

Caching block device access to MTD devices found in drivers/mtd/Kconfig

The configuration item CONFIG_MTD_BLOCK:

• prompt: Caching block device access to MTD devices
• type: tristate
• depends on: CONFIG_BLOCK
• defined in drivers/mtd/Kconfig
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.17, 6.18-rc+HEAD
• modules built: mtd_blkdevs, mtd_blkdevs, mtd_blkdevs, mtdblock, mtdblock, mtdblock

Help text

Although most flash chips have an erase size too large to be useful as block devices, it is possible to use MTD devices which are based on RAM chips in this manner. This block device is a user of MTD devices performing that function.

Note that mounting a JFFS2 filesystem doesn't require using mtdblock. It's possible to mount a rootfs using the MTD device on the "root=" bootargs as "root=mtd2" or "root=mtd:name_of_device".

Later, it may be extended to perform read/erase/modify/write cycles on flash chips to emulate a smaller block size. Needless to say, this is very unsafe, but could be useful for file systems which are almost never written to.

You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (NFTL) instead.

found in arch/cris/arch-v10/drivers/Kconfig

The configuration item CONFIG_MTD_BLOCK:

• prompt:
• type: tristate
• depends on: CONFIG_ETRAX_AXISFLASHMAP
• defined in arch/cris/arch-v10/drivers/Kconfig
• found in Linux kernels: 2.5.75, 2.6.0–2.6.12
• modules built: mtd_blkdevs, mtd_blkdevs, mtd_blkdevs, mtdblock, mtdblock, mtdblock

Help text

Although most flash chips have an erase size too large to be useful as block devices, it is possible to use MTD devices which are based on RAM chips in this manner. This block device is a user of MTD devices performing that function.

At the moment, it is also required for the Journalling Flash File System(s) to obtain a handle on the MTD device when it's mounted (although JFFS and JFFS2 don't actually use any of the functionality of the mtdblock device).

Later, it may be extended to perform read/erase/modify/write cycles on flash chips to emulate a smaller block size. Needless to say, this is very unsafe, but could be useful for file systems which are almost never written to.

You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (NFTL) instead.

found in arch/cris/drivers/Kconfig

The configuration item CONFIG_MTD_BLOCK:

• prompt:
• type: tristate
• depends on: CONFIG_ETRAX_AXISFLASHMAP
• defined in arch/cris/drivers/Kconfig
• found in Linux kernels: 2.5.45–2.5.74
• modules built: mtd_blkdevs, mtd_blkdevs, mtd_blkdevs, mtdblock, mtdblock, mtdblock

Help text

Although most flash chips have an erase size too large to be useful as block devices, it is possible to use MTD devices which are based on RAM chips in this manner. This block device is a user of MTD devices performing that function.

At the moment, it is also required for the Journalling Flash File System(s) to obtain a handle on the MTD device when it's mounted (although JFFS and JFFS2 don't actually use any of the functionality of the mtdblock device).

Later, it may be extended to perform read/erase/modify/write cycles on flash chips to emulate a smaller block size. Needless to say, this is very unsafe, but could be useful for file systems which are almost never written to.

You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (NFTL) instead.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module mtd_blkdevs CONFIG_MTD_BLOCK : arch/cris/arch-v10/drivers/Kconfig : "" # in 2.5.75, 2.6.0–2.6.12
• lkddb module mtd_blkdevs CONFIG_MTD_BLOCK : arch/cris/drivers/Kconfig : "" # in 2.5.71–2.5.74
• lkddb module mtd_blkdevs CONFIG_MTD_BLOCK : drivers/mtd/Kconfig : "Caching block device access to MTD devices" # in 2.5.71–2.5.75, 2.6.0–2.6.19
• lkddb module mtdblock CONFIG_MTD_BLOCK : arch/cris/arch-v10/drivers/Kconfig : "" # in 2.5.75, 2.6.0–2.6.12
• lkddb module mtdblock CONFIG_MTD_BLOCK : arch/cris/drivers/Kconfig : "" # in 2.5.45–2.5.74
• lkddb module mtdblock CONFIG_MTD_BLOCK : drivers/mtd/Kconfig : "Caching block device access to MTD devices" # in 2.5.45–2.5.75, 2.6.0–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.17, 6.18-rc+HEAD

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: