[U-Boot] [PATCH v2 3/8] README: Review the u-boot porting guide list

[Stefan Roese]

On 22.12.2015 00:25, Phil Sutter wrote:
> * There is no boards.cfg anymore, so drop (1).
> * Creating flash.c and u-boot.lds seems not mandatory as well.
> * Adjusting the enumerators for the above implicitly fixed for
>    double items numbered (3).
>
> Signed-off-by: Phil Sutter <phil at nwl.cc>
> ---
>   README | 11 ++++-------
>   1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/README b/README
> index 4fee706..dcc9478 100644
> --- a/README
> +++ b/README
> @@ -5153,14 +5153,11 @@ If the system board that you have is not listed, then you will need
>   to port U-Boot to your hardware platform. To do this, follow these
>   steps:
>
> -1.  Add a new configuration option for your board to the toplevel
> -    "boards.cfg" file, using the existing entries as examples.
> -    Follow the instructions there to keep the boards in order.
> -2.  Create a new directory to hold your board specific code. Add any
> +1.  Create a new directory to hold your board specific code. Add any
>       files you need. In your board directory, you will need at least
> -    the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
> -3.  Create a new configuration file "include/configs/<board>.h" for
> -    your board
> +    the "Makefile" and a "<board>.c".
> +2.  Create a new configuration file "include/configs/<board>.h" for
> +    your board.
>   3.  If you're porting U-Boot to a new CPU, then also create a new
>       directory to hold your CPU specific code. Add any files you need.
>   4.  Run "make <board>_defconfig" with your new name.
>

Seems this documentation is really outdated and needs some further
adjustments. But still, this is definitely the right direction, so:

Reviewed-by: Stefan Roese <sr at denx.de>

Thanks,
Stefan