Searched refs:DiskOnChip (Results 1 – 6 of 6) sorted by relevance
1 M-Systems and Sandisk DiskOnChip devices3 M-System DiskOnChip G3
211 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"216 This is a reimplementation of M-Systems DiskOnChip 2000,223 bool "Advanced detection options for DiskOnChip"227 probe for a DiskOnChip, or to change the detection options. You232 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED236 By default, the probe for DiskOnChip devices will look for a237 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.252 By default, the probe for DiskOnChip devices will look for a253 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.259 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"[all …]
186 You do not need this option for use with the DiskOnChip devices. For198 You do not need this option for use with the DiskOnChip devices. For224 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-230 legal - in the USA you are only permitted to use this on DiskOnChip240 on the DiskOnChip.248 Layer which is used on M-Systems' newer DiskOnChip devices. It255 legal - in the USA you are only permitted to use this on DiskOnChip
161 The new DiskOnChip driver scans the MediaHeader itself, and presents a virtual in find_boot_record()230 The new DiskOnChip driver already scanned the bad block table. Just query it. in find_boot_record()
194 struct DiskOnChip { struct
206 This provides an MTD device driver for the M-Systems DiskOnChip209 The driver provides access to G3 DiskOnChip, distributed by