CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE: Allow BBT writes on DiskOnChip Millennium and 2000TSOP

General informations

The Linux kernel configuration item CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE has multiple definitions:

Allow BBT writes on DiskOnChip Millennium and 2000TSOP found in drivers/mtd/nand/raw/Kconfig

The configuration item CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE:

• prompt: Allow BBT writes on DiskOnChip Millennium and 2000TSOP
• type: bool
• depends on: CONFIG_MTD_NAND_DISKONCHIP
• defined in drivers/mtd/nand/raw/Kconfig
• found in Linux kernels: 4.17–4.20, 5.0–5.19, 6.0–6.11

Help text

On DiskOnChip devices shipped with the INFTL filesystem (Millennium and 2000 TSOP/Alon), Linux reserves some space at the end of the device for the Bad Block Table (BBT). If you have existing INFTL data on your device (created by non-Linux tools such as M-Systems' DOS drivers), your data might overlap the area Linux wants to use for the BBT. If this is a concern for you, leave this option disabled and Linux will not write BBT data into this area. The downside of leaving this option disabled is that if bad blocks are detected by Linux, they will not be recorded in the BBT, which could cause future problems. Once you enable this option, new filesystems (INFTL or others, created in Linux or other operating systems) will not use the reserved area. The only reason not to enable this option is to prevent damage to preexisting filesystems. Even if you leave this disabled, you can enable BBT writes at module load time (assuming you build diskonchip as a module) with the module parameter "inftl_bbt_write=1".

Allow BBT writes on DiskOnChip Millennium and 2000TSOP found in drivers/mtd/nand/Kconfig

The configuration item CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE:

• prompt: Allow BBT writes on DiskOnChip Millennium and 2000TSOP
• type: bool
• depends on: CONFIG_MTD_NAND_DISKONCHIP
• defined in drivers/mtd/nand/Kconfig
• found in Linux kernels: 2.6.8–2.6.39, 3.0–3.19, 4.0–4.16

Help text

On DiskOnChip devices shipped with the INFTL filesystem (Millennium and 2000 TSOP/Alon), Linux reserves some space at the end of the device for the Bad Block Table (BBT). If you have existing INFTL data on your device (created by non-Linux tools such as M-Systems' DOS drivers), your data might overlap the area Linux wants to use for the BBT. If this is a concern for you, leave this option disabled and Linux will not write BBT data into this area. The downside of leaving this option disabled is that if bad blocks are detected by Linux, they will not be recorded in the BBT, which could cause future problems. Once you enable this option, new filesystems (INFTL or others, created in Linux or other operating systems) will not use the reserved area. The only reason not to enable this option is to prevent damage to preexisting filesystems. Even if you leave this disabled, you can enable BBT writes at module load time (assuming you build diskonchip as a module) with the module parameter "inftl_bbt_write=1".

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: