gpio: am43xx: expand gpio support

[karo-tx-uboot.git] / doc / README.generic-board

diff --git a/doc/README.generic-board b/doc/README.generic-board
index 50d3a26849d7bf5d234edcd1f85243c960d5f375..734f1aa9249aea3f7bd34351132c9350ab5d5b24 100644 (file)
--- a/doc/README.generic-board
+++ b/doc/README.generic-board
@@ -17,7 +17,7 @@ architecture-specific board.c file before October 2014.
 Background
 ----------
 
 Background
 ----------
 

-U-Boot has tranditionally had a board.c file for each architecture. This has
+U-Boot has traditionally had a board.c file for each architecture. This has

 introduced quite a lot of duplication, with each architecture tending to do
 initialisation slightly differently. To address this, a new 'generic board
 init' feature was introduced a year ago in March 2013 (further motivation is
 introduced quite a lot of duplication, with each architecture tending to do
 initialisation slightly differently. To address this, a new 'generic board
 init' feature was introduced a year ago in March 2013 (further motivation is


@@ -36,23 +36,26 @@ fields which are common to all architectures. Architecture-specific fields
 have been moved to separate structures.
 
 
 have been moved to separate structures.
 
 

-Supported Arcthitectures
+Supported Architectures

 ------------------------
 
 If you are unlucky then your architecture may not support generic board.
 ------------------------
 
 If you are unlucky then your architecture may not support generic board.

-The following architectures are supported at the time of writing:
+The following architectures are supported now:

 
    arc
    arm
 
    arc
    arm

+   avr32
+   blackfin
+   m68k
+   microblaze
+   mips
+   nios2

    powerpc
    sandbox
    x86
 
    powerpc
    sandbox
    x86
 

-If your architecture is not supported, you need to adjust your
-arch/<arch>/config.mk file to include:
-
-   __HAVE_ARCH_GENERIC_BOARD := y
-
+If your architecture is not supported, you need to select
+HAVE_GENERIC_BOARD in arch/Kconfig

 and test it with a suitable board, as follows.
 
 
 and test it with a suitable board, as follows.
 
 


@@ -102,12 +105,12 @@ places.
 initialisation is painful since it must be independently added in 10
 places.
 
 initialisation is painful since it must be independently added in 10
 places.
 

-3. As time goes by the architectures naturely diverge since there is limited
-pressure to compare features or even CONFIG options against simiilar things
+3. As time goes by the architectures naturally diverge since there is limited
+pressure to compare features or even CONFIG options against similar things

 in other board.c files.
 
 4. New architectures must implement all the features all over again, and
 in other board.c files.
 
 4. New architectures must implement all the features all over again, and

-sometimes in subtley different ways. This places an unfair burden on getting
+sometimes in subtle different ways. This places an unfair burden on getting

 a new architecture fully functional and running with U-Boot.
 
 5. While it is a bit of a tricky change, I believe it is worthwhile and
 a new architecture fully functional and running with U-Boot.
 
 5. While it is a bit of a tricky change, I believe it is worthwhile and