Am Freitag, den 29.06.2012, 09:37 +0200 schrieb Michal Simek:
> Call emaclite FDT registration when CONFIG_OF_CONTROL is used.
>
> Signed-off-by: Michal Simek <mon...@monstr.eu>
> ---
> .../xilinx/microblaze-generic/microblaze-generic.c | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/board/xilinx/microblaze-generic/microblaze-generic.c
> b/board/xilinx/microblaze-generic/microblaze-generic.c
> index a1e2bfe..4a719ba 100644
> --- a/board/xilinx/microblaze-generic/microblaze-generic.c
> +++ b/board/xilinx/microblaze-generic/microblaze-generic.c
> @@ -73,6 +73,9 @@ int board_eth_init(bd_t *bis)
> {
> int ret = 0;
>
> +#ifdef CONFIG_OF_CONTROL
> + ret |= xilinx_emaclite_init(bis);
> +#else
First of all: I've successful tested on an AXI system on Avnet S6LX9
micro-module.
Now some words to the different configuration strategy. I prefer a
seperation between the ongoing development without device tree support
and the upcoming development with fdt support.
Could you split the development in the context of boards, for example:
OLD: Development w/o fdt in:
- board/xilinx/microblaze-generic/*
- configuration in include/configs/microblaze-generic.h
NEW: Development with fdt in:
- board/xilinx/microblaze-fdt/*
- configuration in include/configs/microblaze-fdt.h
So you can start with a really clean and slimmed board configuration for
fdt development (especially the content of config header) and the old
generic board support would be retained. Anytime in the future, when the
generic configuration will become obsolete you can remove it.
br,
Stephan
> #ifdef CONFIG_XILINX_AXIEMAC
> ret |= xilinx_axiemac_initialize(bis, XILINX_AXIEMAC_BASEADDR,
> XILINX_AXIDMA_BASEADDR);
> @@ -125,6 +128,6 @@ int board_eth_init(bd_t *bis)
> # endif
> # endif
> #endif
> -
> +#endif
> return ret;
> }
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
