fw_env: calculate default number of env sectors

[karo-tx-uboot.git] / doc / README.at91-soc

diff --git a/doc/README.at91-soc b/doc/README.at91-soc
index 425fc588f04b0b01483f7ca7bbc5643ece76c225..ab3f71342226d3d9bd3db7b32b1da0b67fc80b45 100644 (file)
--- a/doc/README.at91-soc
+++ b/doc/README.at91-soc
@@ -40,25 +40,9 @@ The method for updating
 4. Convert arch, driver and boards file to new SoC
 5. remove legacy code, if all boards and drives are ready
 
- Join AT91 and AT91RM9200 SoC
-==============================
+2013-10-30 Andreas Bießmann <andreas.devel@googlemail.com>:
 
-Approximately 95 percent of AT91 and AT91RM9200 SoC parts are the same.
-So, we should use the chance, to join both archs togetter.
-
-To do this follow step needed:
-
-1. change Makefile
-       @$(MKCONFIG) $(@:_config=) arm arm920t board vendor at91rm9200
-  to
-       @$(MKCONFIG) $(@:_config=) arm arm920t board vendor at91
-2. remove CONFIG_AT91_LEGACY in board config
-3. convert boards file to new SoC access
-4. convert or change drivers
-
-To support the joining process, a new SoC dir (at91) has been adding to
-arm920t arch directory. This directory contains files like at91rm9200 dir, but
-uses the new c structure Soc access. The advantage of this is, we don't merge
-old Soc access code and new code while the board are not converted.
-Finally we can delete the whole at91rm9200 dir, if all board support the
-new AT91-SoC access.
+The goal is almost reached, we could remove the CONFIG_AT91_LEGACY switch but
+remain the CONFIG_ATMEL_LEGACY switch until the GPIO disaster is fixed. The
+AT91 spi driver has also some CONFIG_ATMEL_LEGACY stuff left, so another point
+to fix until this README can be removed.