summaryrefslogtreecommitdiffstats
path: root/qemu/roms/u-boot/doc/README.cfi
diff options
context:
space:
mode:
Diffstat (limited to 'qemu/roms/u-boot/doc/README.cfi')
-rw-r--r--qemu/roms/u-boot/doc/README.cfi29
1 files changed, 0 insertions, 29 deletions
diff --git a/qemu/roms/u-boot/doc/README.cfi b/qemu/roms/u-boot/doc/README.cfi
deleted file mode 100644
index d087ff0d6..000000000
--- a/qemu/roms/u-boot/doc/README.cfi
+++ /dev/null
@@ -1,29 +0,0 @@
-The common CFI driver provides this weak default implementation for
-flash_cmd_reset():
-
-void __flash_cmd_reset(flash_info_t *info)
-{
- /*
- * We do not yet know what kind of commandset to use, so we issue
- * the reset command in both Intel and AMD variants, in the hope
- * that AMD flash roms ignore the Intel command.
- */
- flash_write_cmd(info, 0, 0, AMD_CMD_RESET);
- flash_write_cmd(info, 0, 0, FLASH_CMD_RESET);
-}
-void flash_cmd_reset(flash_info_t *info)
- __attribute__((weak,alias("__flash_cmd_reset")));
-
-
-Some flash chips seems to have trouble with this reset sequence. In this case
-the board specific code can override this weak default version with a board
-specific function. For example the digsy_mtc board equipped with the M29W128GH
-from Numonyx needs this version to function properly:
-
-void flash_cmd_reset(flash_info_t *info)
-{
- flash_write_cmd(info, 0, 0, AMD_CMD_RESET);
-}
-
-see also:
-http://www.mail-archive.com/u-boot@lists.denx.de/msg24368.html