[U-Boot] [PATCH 8/8] xtensa: add support for the 'xtfpga' evaluation board

[Max Filippov]

Hi Michal,

On Wed, Jul 13, 2016 at 08:35:37AM +0200, Michal Simek wrote:
> On 8.7.2016 17:42, Max Filippov wrote:
> > From: Chris Zankel <chris at zankel.net>
> > 
> > The 'xtfpga' board is actually a set of FPGA evaluation boards that
> > can be configured to run an Xtensa processor.
> > 
> >  - Avnet Xilinx LX60
> >  - Avnet Xilinx LX110
> >  - Avnet Xilinx LX200
> >  - Xilinx ML605
> >  - Xilinx KC705
> > 
> > These boards share the same components (open-ethernet, ns16550 serial,
> > lcd display, flash, etc.).
> > 
> > Signed-off-by: Chris Zankel <chris at zankel.net>
> > Signed-off-by: Max Filippov <jcmvbkbc at gmail.com>
> > ---

[...]

> > diff --git a/board/cadence/xtfpga/Kconfig b/board/cadence/xtfpga/Kconfig
> > new file mode 100644
> > index 0000000..a7b65ef
> > --- /dev/null
> > +++ b/board/cadence/xtfpga/Kconfig
> > @@ -0,0 +1,43 @@
> > +if TARGET_XTFPGA
> > +
> > +choice
> > +	prompt "XTFPGA board type select"
> > +
> > +config XTFPGA_LX60
> > +	bool "Support Avnet LX60"
> > +	select HAVE_SYS_ASCDISP
> > +config XTFPGA_LX110
> > +	bool "Support Avnet LX110"
> > +	select HAVE_SYS_ASCDISP
> > +config XTFPGA_LX200
> > +	bool "Support Avnet LX200"
> > +config XTFPGA_ML605
> > +	bool "Support Xilinx ML605"
> > +	select HAVE_SYS_ASCDISP
> > +config XTFPGA_KC705
> > +	bool "Support Xilinx KC705"
> > +	select HAVE_SYS_ASCDISP
> > +
> > +endchoice
> > +
> > +config SYS_BOARD
> > +	string
> > +	default "xtfpga"
> > +
> > +config SYS_VENDOR
> > +	string
> > +	default "cadence"
> > +
> > +config SYS_CONFIG_NAME
> > +	string
> > +	default "xtfpga"
> > +V
> > +config BOARD_SDRAM_SIZE
> > +	hex
> > +	default 0x04000000 if XTFPGA_LX60
> > +	default 0x03000000 if XTFPGA_LX110
> > +	default 0x06000000 if XTFPGA_LX200
> > +	default 0x18000000 if XTFPGA_ML605
> > +	default 0x38000000 if XTFPGA_KC705
> 
> You should read this directly from DTS files.
> The same you have below in config.

We have it this way so that we could calculate the location of monitor
below the top of available RAM at compile time and use it in the linker
script. Thus we avoid doing generic relocations at startup and just copy
monitor to the address it was linked for.

-- 
Thanks.
-- Max