Searched refs:DiskOnChip (Results 1 – 7 of 7) sorted by relevance
1 M-Systems and Sandisk DiskOnChip devices3 M-System DiskOnChip G3
161 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"166 This is a reimplementation of M-Systems DiskOnChip 2000,173 bool "Advanced detection options for DiskOnChip"177 probe for a DiskOnChip, or to change the detection options. You182 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED186 By default, the probe for DiskOnChip devices will look for a187 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.202 By default, the probe for DiskOnChip devices will look for a203 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.209 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"[all …]
189 You do not need this option for use with the DiskOnChip devices. For201 You do not need this option for use with the DiskOnChip devices. For227 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-233 legal - in the USA you are only permitted to use this on DiskOnChip243 on the DiskOnChip.251 Layer which is used on M-Systems' newer DiskOnChip devices. It258 legal - in the USA you are only permitted to use this on DiskOnChip
160 The new DiskOnChip driver scans the MediaHeader itself, and presents a virtual in find_boot_record()232 The new DiskOnChip driver already scanned the bad block table. Just query it. in find_boot_record()
194 struct DiskOnChip { struct
213 This provides an MTD device driver for the M-Systems DiskOnChip216 The driver provides access to G3 DiskOnChip, distributed by
451 (device). This applies to various DiskOnChip devices.
