linux-sunxi/u-boot-sunxi
1
0
Fork 0
mirror of https://github.com/linux-sunxi/u-boot-sunxi.git synced 2024-02-12 11:16:03 +08:00
Code Issues Projects Releases Wiki Activity

README: Review the u-boot porting guide list

Browse Source 
* 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@nwl.cc>
Acked-by: Stefan Roese <sr@denx.de>
Reviewed-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
Phil Sutter
2015-12-25 14:41:18 +01:00
committed by Stefan Roese
parent 1113146793
commit 3c1496cd4d
1 changed files with 4 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README
View File

@ -5118,14 +5118,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 to port U-Boot to your hardware platform. To do this, follow these
steps: steps:
1. Add a new configuration option for your board to the toplevel 1. Create a new directory to hold your board specific code. Add any
"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
files you need. In your board directory, you will need at least files you need. In your board directory, you will need at least
the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds". the "Makefile" and a "<board>.c".
3. Create a new configuration file "include/configs/<board>.h" for 2. Create a new configuration file "include/configs/<board>.h" for
your board your board.
3. If you're porting U-Boot to a new CPU, then also create a new 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. directory to hold your CPU specific code. Add any files you need.
4. Run "make <board>_defconfig" with your new name. 4. Run "make <board>_defconfig" with your new name.