On Tue, 2015-04-14 at 04:50PM +0900, Masahiro Yamada wrote:
> Separate CONFIG_TARGET_ZYNQ_{ZC702,ZC706} which is necessary
> for the next commit. Adjust doc/README.zynq too.
>
> Signed-off-by: Masahiro Yamada <yamada.masah...@socionext.com>
> ---
>
> Changes in v2: None
>
> arch/arm/cpu/armv7/zynq/Kconfig | 9 ++++++---
> configs/{zynq_zc70x_defconfig => zynq_zc702_defconfig} | 2 +-
> configs/zynq_zc706_defconfig | 11 +++++++++++
> doc/README.zynq | 15 ++++-----------
> 4 files changed, 22 insertions(+), 15 deletions(-)
> rename configs/{zynq_zc70x_defconfig => zynq_zc702_defconfig} (88%)
> create mode 100644 configs/zynq_zc706_defconfig
>
> diff --git a/arch/arm/cpu/armv7/zynq/Kconfig b/arch/arm/cpu/armv7/zynq/Kconfig
> index 3a52535..ab4768a 100644
> --- a/arch/arm/cpu/armv7/zynq/Kconfig
> +++ b/arch/arm/cpu/armv7/zynq/Kconfig
> @@ -9,8 +9,11 @@ config TARGET_ZYNQ_ZED
> config TARGET_ZYNQ_MICROZED
> bool "Zynq MicroZed"
>
> -config TARGET_ZYNQ_ZC70X
> - bool "Zynq ZC702/ZC706 Board"
> +config TARGET_ZYNQ_ZC702
> + bool "Zynq ZC702 Board"
> +
> +config TARGET_ZYNQ_ZC706
> + bool "Zynq ZC706 Board"
Is there a good way to make this more friendly towards a user who is
familiar with the current flow? By simply removing it, we'll get plenty
of support requests asking what happened. Also, it would void all the
documentation we have in wikis etc. A more soft migration path would be
better.
Sören
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
