[Buildroot] [PATCH 0/2] zynq: some fixes and update readme.txt for custom ps7_init guide

[Buildroot] [PATCH 0/2] zynq: some fixes and update readme.txt for custom ps7_init guide

[Masahiro Yamada]

Matthew Weber reviewed v1 of my Zynq update series, and mentioned
to add information about custom ps7_init files.

So, I was working on v2 and was almost about to send v2.
But I was a few hours late...  V1 is now in the mailine.

So, I am sending a follow-up series.

1/2 is a fix I was planning to squash into v1.

2/2 is a readme update to revive custom ps7_init information.
(Matt said he would send it, but I had already prepared it,
so here it is just in case.  If he would like to replace it
with a better one, that is fine, though.)



Masahiro Yamada (2):
  zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
  zynq: document how to use custom ps7_init files

 board/zynq/readme.txt           | 46 ++++++++++++++++++++++++++++++++++-------
 configs/zynq_microzed_defconfig |  3 ++-
 configs/zynq_zc706_defconfig    |  5 +++--
 configs/zynq_zed_defconfig      |  3 ++-
 4 files changed, 45 insertions(+), 12 deletions(-)

-- 
1.9.1

[Buildroot] [PATCH 1/2] zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG

[Masahiro Yamada]

The recent U-Boot adopts Kconfig for its configuration system.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
---

 board/zynq/readme.txt           | 4 ++--
 configs/zynq_microzed_defconfig | 3 ++-
 configs/zynq_zc706_defconfig    | 5 +++--
 configs/zynq_zed_defconfig      | 3 ++-
 4 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/board/zynq/readme.txt b/board/zynq/readme.txt
index 73f8bf3..51e28b6 100644
--- a/board/zynq/readme.txt
+++ b/board/zynq/readme.txt
@@ -11,11 +11,11 @@ board even if it is not listed above.  Major Zynq-based boards are supported by
 U-Boot, and their Device Trees are merged in Linux Kernel.  If your board is the
 case, booting the kernel is a piece of cake.  All you need to do is to change:
  - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
- - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARDNAME)
+ - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_KCONFIG)
 
 Steps to create a working system for a Zynq board:
 
-1) Configuration (do one of the followings)
+1) Configuration (do one of the following)
     make zynq_zc706_defconfig     (ZC706)
     make zynq_zed_defconfig       (Zedboard)
     make zynq_microzed_defconfig  (MicroZed)
diff --git a/configs/zynq_microzed_defconfig b/configs/zynq_microzed_defconfig
index fa25857..5efc0d4 100644
--- a/configs/zynq_microzed_defconfig
+++ b/configs/zynq_microzed_defconfig
@@ -16,10 +16,11 @@ BR2_TARGET_ROOTFS_CPIO=y
 BR2_TARGET_ROOTFS_CPIO_GZIP=y
 BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
 BR2_TARGET_UBOOT=y
-BR2_TARGET_UBOOT_BOARDNAME="zynq_microzed"
+BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
 BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2016.2"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_microzed"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_IMG=y
 BR2_TARGET_UBOOT_SPL=y
diff --git a/configs/zynq_zc706_defconfig b/configs/zynq_zc706_defconfig
index 4ac2fe8..578f042 100644
--- a/configs/zynq_zc706_defconfig
+++ b/configs/zynq_zc706_defconfig
@@ -1,7 +1,7 @@
 BR2_arm=y
 BR2_cortex_a9=y
-BR2_ARM_ENABLE_VFP=y
 BR2_ARM_ENABLE_NEON=y
+BR2_ARM_ENABLE_VFP=y
 BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
 BR2_LINUX_KERNEL=y
@@ -17,10 +17,11 @@ BR2_TARGET_ROOTFS_CPIO=y
 BR2_TARGET_ROOTFS_CPIO_GZIP=y
 BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
 BR2_TARGET_UBOOT=y
-BR2_TARGET_UBOOT_BOARDNAME="zynq_zc706"
+BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
 BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2016.2"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_zc706"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_IMG=y
 BR2_TARGET_UBOOT_SPL=y
diff --git a/configs/zynq_zed_defconfig b/configs/zynq_zed_defconfig
index 84859bb..7ce3365 100644
--- a/configs/zynq_zed_defconfig
+++ b/configs/zynq_zed_defconfig
@@ -16,10 +16,11 @@ BR2_TARGET_ROOTFS_CPIO=y
 BR2_TARGET_ROOTFS_CPIO_GZIP=y
 BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
 BR2_TARGET_UBOOT=y
-BR2_TARGET_UBOOT_BOARDNAME="zynq_zed"
+BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
 BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2016.2"
+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_zed"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_IMG=y
 BR2_TARGET_UBOOT_SPL=y
-- 
1.9.1

[Buildroot] [PATCH 2/2] zynq: document how to use custom ps7_init files

[Masahiro Yamada]

Since U-Boot supported SPL for Zynq boards at v2014.04 release, it
became much easier to build a system.  At that time, however, users
still needed to manually copy ps7_init.c/h to the U-Boot source tree
to generate a working SPL image because ps7_init.c/h output from
Xilinx tools are not compatible with GPL.

Later, the license problem was solved when Xilinx tools became able
to output the GPL-compatible variants (ps7_init_gpl.c/h) as well.
U-Boot v2015.07 or later includes ps7_init_gpl.c/h for major Zynq
boards so that users can build a boot image straight away.

Now Buildroot supports 3 boards (Zedboard, MicroZed, ZC706) without
any manual intervention.  This is a good thing itself, but commit
b9cd72cdbfe3 ("zynq_zc706: bump U-Boot to xilinx-v2016.2") entirely
dropped the information about custom ps7_init files.

This commit provides up-to-date guidance for how to customize the
ps7_init files.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
---

 board/zynq/readme.txt | 44 +++++++++++++++++++++++++++++++++++++-------
 1 file changed, 37 insertions(+), 7 deletions(-)

diff --git a/board/zynq/readme.txt b/board/zynq/readme.txt
index 51e28b6..debb163 100644
--- a/board/zynq/readme.txt
+++ b/board/zynq/readme.txt
@@ -6,13 +6,6 @@ Currently, three boards are natively supported by Buildroot:
  - Avnet ZedBoard (zynq_zed_defconfig)
  - Avnet MicroZed (zynq_microzed_defconfig)
 
-The following build procedure focuses on them, but you can adjust it to your
-board even if it is not listed above.  Major Zynq-based boards are supported by
-U-Boot, and their Device Trees are merged in Linux Kernel.  If your board is the
-case, booting the kernel is a piece of cake.  All you need to do is to change:
- - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
- - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_KCONFIG)
-
 Steps to create a working system for a Zynq board:
 
 1) Configuration (do one of the following)
@@ -50,3 +43,40 @@ References:
 
  - Zedboard/Microzed information including schematics, reference designs, and
    manuals are available from http://www.zedboard.org .
+
+Support for other boards:
+
+You may want to build a system for other boards (for ex. Digilent Zybo board).
+U-Boot supports major Zynq-based boards, and their Device Trees are mostly
+merged in Linux Kernel.  If your board is the case, booting the kernel is a
+piece of cake.  All you need to do is to tweak:
+ - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
+ - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_DEFCONFIG)
+
+Custom ps7_init_gpl.c/h support:
+
+To generate a working boot.bin image, ps7_init_gpl.c/h are required in the
+U-Boot source tree.  Those files are output from the Xilinx tools, but for
+convenience, U-Boot includes the default ps7_init_gpl.c/h of popular boards.
+See board/xilinx/zynq/ directory of U-Boot for natively supported ps7_init
+files.  If the ps7_init files for your board are not found in U-Boot, you need
+to add them by yourself.  (You can still override the existing ones if you want
+to customize them for your purpose.)
+
+1) Start with a defconfig supported by Buildroot (for ex. Zedboard)
+    make zynq_zed_defconfig
+
+2) make uboot-menuconfig
+    Visit the following menu and enable CONFIG_ZYNQ_CUSTOM_INIT.
+
+    ARM architecture  --->
+       [*] Use custom ps7_init provided by Xilinx tool
+
+3) Copy ps7_init_gpl.c/h generated by the Xilinx tools into
+   output/build/uboot-xilinx-v2016.2/board/xilinx/zynq/custom_hw_platform/
+
+4) make
+
+*Notice*
+While the build will successfully complete with/without the ps7_init_gpl.*
+files, the boot.bin generated without ones will not be functional at all.
-- 
1.9.1

[Buildroot] [PATCH 1/2] zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG

[Matthew Weber]

 All,

On Sun, Jul 31, 2016 at 12:43 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> The recent U-Boot adopts Kconfig for its configuration system.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
>  board/zynq/readme.txt           | 4 ++--
>  configs/zynq_microzed_defconfig | 3 ++-
>  configs/zynq_zc706_defconfig    | 5 +++--
>  configs/zynq_zed_defconfig      | 3 ++-
>  4 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/board/zynq/readme.txt b/board/zynq/readme.txt
> index 73f8bf3..51e28b6 100644
> --- a/board/zynq/readme.txt
> +++ b/board/zynq/readme.txt
> @@ -11,11 +11,11 @@ board even if it is not listed above.  Major Zynq-based boards are supported by
>  U-Boot, and their Device Trees are merged in Linux Kernel.  If your board is the
>  case, booting the kernel is a piece of cake.  All you need to do is to change:
>   - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
> - - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARDNAME)
> + - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_KCONFIG)
>
>  Steps to create a working system for a Zynq board:
>
> -1) Configuration (do one of the followings)
> +1) Configuration (do one of the following)
>      make zynq_zc706_defconfig     (ZC706)
>      make zynq_zed_defconfig       (Zedboard)
>      make zynq_microzed_defconfig  (MicroZed)
> diff --git a/configs/zynq_microzed_defconfig b/configs/zynq_microzed_defconfig
> index fa25857..5efc0d4 100644
> --- a/configs/zynq_microzed_defconfig
> +++ b/configs/zynq_microzed_defconfig
> @@ -16,10 +16,11 @@ BR2_TARGET_ROOTFS_CPIO=y
>  BR2_TARGET_ROOTFS_CPIO_GZIP=y
>  BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
>  BR2_TARGET_UBOOT=y
> -BR2_TARGET_UBOOT_BOARDNAME="zynq_microzed"
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>  BR2_TARGET_UBOOT_CUSTOM_GIT=y
>  BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
>  BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2016.2"
> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_microzed"
>  BR2_TARGET_UBOOT_NEEDS_DTC=y
>  BR2_TARGET_UBOOT_FORMAT_IMG=y
>  BR2_TARGET_UBOOT_SPL=y
> diff --git a/configs/zynq_zc706_defconfig b/configs/zynq_zc706_defconfig
> index 4ac2fe8..578f042 100644
> --- a/configs/zynq_zc706_defconfig
> +++ b/configs/zynq_zc706_defconfig
> @@ -1,7 +1,7 @@
>  BR2_arm=y
>  BR2_cortex_a9=y
> -BR2_ARM_ENABLE_VFP=y
>  BR2_ARM_ENABLE_NEON=y
> +BR2_ARM_ENABLE_VFP=y
>  BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
>  BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
>  BR2_LINUX_KERNEL=y
> @@ -17,10 +17,11 @@ BR2_TARGET_ROOTFS_CPIO=y
>  BR2_TARGET_ROOTFS_CPIO_GZIP=y
>  BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
>  BR2_TARGET_UBOOT=y
> -BR2_TARGET_UBOOT_BOARDNAME="zynq_zc706"
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>  BR2_TARGET_UBOOT_CUSTOM_GIT=y
>  BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
>  BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2016.2"
> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_zc706"
>  BR2_TARGET_UBOOT_NEEDS_DTC=y
>  BR2_TARGET_UBOOT_FORMAT_IMG=y
>  BR2_TARGET_UBOOT_SPL=y
> diff --git a/configs/zynq_zed_defconfig b/configs/zynq_zed_defconfig
> index 84859bb..7ce3365 100644
> --- a/configs/zynq_zed_defconfig
> +++ b/configs/zynq_zed_defconfig
> @@ -16,10 +16,11 @@ BR2_TARGET_ROOTFS_CPIO=y
>  BR2_TARGET_ROOTFS_CPIO_GZIP=y
>  BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
>  BR2_TARGET_UBOOT=y
> -BR2_TARGET_UBOOT_BOARDNAME="zynq_zed"
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>  BR2_TARGET_UBOOT_CUSTOM_GIT=y
>  BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
>  BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2016.2"
> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_zed"
>  BR2_TARGET_UBOOT_NEEDS_DTC=y
>  BR2_TARGET_UBOOT_FORMAT_IMG=y
>  BR2_TARGET_UBOOT_SPL=y
> --
> 1.9.1
>

Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com>


-- 
Matthew L Weber / Pr Software Engineer
Airborne Information Systems / Security Systems and Software / Secure Platforms
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
www.rockwellcollins.com

Note: Any Export License Required Information and License Restricted
Third Party Intellectual Property (TPIP) content must be encrypted and
sent to matthew.weber at corp.rockwellcollins.com.

[Buildroot] [PATCH 2/2] zynq: document how to use custom ps7_init files

[Matthew Weber]

Masahiro,

On Sun, Jul 31, 2016 at 12:43 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> Since U-Boot supported SPL for Zynq boards at v2014.04 release, it
> became much easier to build a system.  At that time, however, users
> still needed to manually copy ps7_init.c/h to the U-Boot source tree
> to generate a working SPL image because ps7_init.c/h output from
> Xilinx tools are not compatible with GPL.
>
> Later, the license problem was solved when Xilinx tools became able
> to output the GPL-compatible variants (ps7_init_gpl.c/h) as well.
> U-Boot v2015.07 or later includes ps7_init_gpl.c/h for major Zynq
> boards so that users can build a boot image straight away.
>
> Now Buildroot supports 3 boards (Zedboard, MicroZed, ZC706) without
> any manual intervention.  This is a good thing itself, but commit
> b9cd72cdbfe3 ("zynq_zc706: bump U-Boot to xilinx-v2016.2") entirely
> dropped the information about custom ps7_init files.
>
> This commit provides up-to-date guidance for how to customize the
> ps7_init files.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
>  board/zynq/readme.txt | 44 +++++++++++++++++++++++++++++++++++++-------
>  1 file changed, 37 insertions(+), 7 deletions(-)
>
> diff --git a/board/zynq/readme.txt b/board/zynq/readme.txt
> index 51e28b6..debb163 100644
> --- a/board/zynq/readme.txt
> +++ b/board/zynq/readme.txt
> @@ -6,13 +6,6 @@ Currently, three boards are natively supported by Buildroot:
>   - Avnet ZedBoard (zynq_zed_defconfig)
>   - Avnet MicroZed (zynq_microzed_defconfig)

Did you mean to remove the previous two lines?

>
> -The following build procedure focuses on them, but you can adjust it to your
> -board even if it is not listed above.  Major Zynq-based boards are supported by
> -U-Boot, and their Device Trees are merged in Linux Kernel.  If your board is the
> -case, booting the kernel is a piece of cake.  All you need to do is to change:
> - - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
> - - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_KCONFIG)
> -
>  Steps to create a working system for a Zynq board:
>
>  1) Configuration (do one of the following)
> @@ -50,3 +43,40 @@ References:
>
>   - Zedboard/Microzed information including schematics, reference designs, and
>     manuals are available from http://www.zedboard.org .

Did you mean to remove this line?

> +
> +Support for other boards:
> +
> +You may want to build a system for other boards (for ex. Digilent Zybo board).

Reword:
If you want to build a system for other boards.....

> +U-Boot supports major Zynq-based boards, and their Device Trees are mostly
> +merged in Linux Kernel.  If your board is the case, booting the kernel is a
> +piece of cake.  All you need to do is to tweak:

Reword:
Most major Zynq-based boards have U-Boot and Kernel support.  If your
board happens to be supported, booting the kernel and using U-Boot
just requires the following Buildroot updates:

> + - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
> + - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_DEFCONFIG)
> +
> +Custom ps7_init_gpl.c/h support:
> +
> +To generate a working boot.bin image, ps7_init_gpl.c/h are required in the
> +U-Boot source tree.  Those files are output from the Xilinx tools, but for
> +convenience, U-Boot includes the default ps7_init_gpl.c/h of popular boards.

Please add the following sentence:
These files may need to be updated for any programmable logic
customizations which impact ps7_init (clock/pin setup & mapping/AXI
bridge setup/etc).

> +See board/xilinx/zynq/ directory of U-Boot for natively supported ps7_init
> +files.  If the ps7_init files for your board are not found in U-Boot, you need
> +to add them by yourself.  (You can still override the existing ones if you want
> +to customize them for your purpose.)
> +
> +1) Start with a defconfig supported by Buildroot (for ex. Zedboard)
> +    make zynq_zed_defconfig
> +
> +2) make uboot-menuconfig
> +    Visit the following menu and enable CONFIG_ZYNQ_CUSTOM_INIT.
> +
> +    ARM architecture  --->
> +       [*] Use custom ps7_init provided by Xilinx tool
> +
> +3) Copy ps7_init_gpl.c/h generated by the Xilinx tools into
> +   output/build/uboot-xilinx-v2016.2/board/xilinx/zynq/custom_hw_platform/

Update:
 output/build/uboot-xilinx-<pkg version>/board/xilinx/zynq/custom_hw_platform/

> +
> +4) make
> +
> +*Notice*
> +While the build will successfully complete with/without the ps7_init_gpl.*
> +files, the boot.bin generated without ones will not be functional at all.
> --
> 1.9.1
>

Otherwise looks good, care to update for a v2?


-- 
Matthew L Weber / Pr Software Engineer
Airborne Information Systems / Security Systems and Software / Secure Platforms
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
www.rockwellcollins.com

Note: Any Export License Required Information and License Restricted
Third Party Intellectual Property (TPIP) content must be encrypted and
sent to matthew.weber at corp.rockwellcollins.com.

[Buildroot] [PATCH 2/2] zynq: document how to use custom ps7_init files

[Masahiro Yamada]

Hi Matthew,

Thanks for your comments!


2016-08-02 11:10 GMT+09:00 Matthew Weber <matthew.weber@rockwellcollins.com>:
> Masahiro,
>
> On Sun, Jul 31, 2016 at 12:43 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>> Since U-Boot supported SPL for Zynq boards at v2014.04 release, it
>> became much easier to build a system.  At that time, however, users
>> still needed to manually copy ps7_init.c/h to the U-Boot source tree
>> to generate a working SPL image because ps7_init.c/h output from
>> Xilinx tools are not compatible with GPL.
>>
>> Later, the license problem was solved when Xilinx tools became able
>> to output the GPL-compatible variants (ps7_init_gpl.c/h) as well.
>> U-Boot v2015.07 or later includes ps7_init_gpl.c/h for major Zynq
>> boards so that users can build a boot image straight away.
>>
>> Now Buildroot supports 3 boards (Zedboard, MicroZed, ZC706) without
>> any manual intervention.  This is a good thing itself, but commit
>> b9cd72cdbfe3 ("zynq_zc706: bump U-Boot to xilinx-v2016.2") entirely
>> dropped the information about custom ps7_init files.
>>
>> This commit provides up-to-date guidance for how to customize the
>> ps7_init files.
>>
>> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>> ---
>>
>>  board/zynq/readme.txt | 44 +++++++++++++++++++++++++++++++++++++-------
>>  1 file changed, 37 insertions(+), 7 deletions(-)
>>
>> diff --git a/board/zynq/readme.txt b/board/zynq/readme.txt
>> index 51e28b6..debb163 100644
>> --- a/board/zynq/readme.txt
>> +++ b/board/zynq/readme.txt
>> @@ -6,13 +6,6 @@ Currently, three boards are natively supported by Buildroot:
>>   - Avnet ZedBoard (zynq_zed_defconfig)
>>   - Avnet MicroZed (zynq_microzed_defconfig)
>
> Did you mean to remove the previous two lines?


No.  '-' is for itemization.



>>
>> -The following build procedure focuses on them, but you can adjust it to your
>> -board even if it is not listed above.  Major Zynq-based boards are supported by
>> -U-Boot, and their Device Trees are merged in Linux Kernel.  If your board is the
>> -case, booting the kernel is a piece of cake.  All you need to do is to change:
>> - - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
>> - - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_KCONFIG)
>> -
>>  Steps to create a working system for a Zynq board:
>>
>>  1) Configuration (do one of the following)
>> @@ -50,3 +43,40 @@ References:
>>
>>   - Zedboard/Microzed information including schematics, reference designs, and
>>     manuals are available from http://www.zedboard.org .
>
> Did you mean to remove this line?

Not at all.
I think the patch format is not broken
because this was sent by "git send-email".


> Otherwise looks good, care to update for a v2?



I am OK with all the suggestions for reword.


If you do not mind, I'd like to hand over this to you.
Could you rephrase them in a way you think better, and send v2 please?

I am not a native English speaker and I believe you will do a better job.



-- 
Best Regards
Masahiro Yamada

[Buildroot] [PATCH 1/2] zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG

[Masahiro Yamada]

Hi Thomas,

2016-08-02 10:57 GMT+09:00 Matthew Weber <matthew.weber@rockwellcollins.com>:
>  All,
>
> On Sun, Jul 31, 2016 at 12:43 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>> The recent U-Boot adopts Kconfig for its configuration system.
>>
>> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>>
>
> Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com>
>


Setting aside 2/2,
1/2 (this one) is apparently a bug fix and Matt reviewed it,
so isn't it ready for v2016.08 ?



-- 
Best Regards
Masahiro Yamada

[Buildroot] [PATCH 1/2] zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG

[Thomas Petazzoni]

Hello,

On Wed, 10 Aug 2016 21:31:16 +0900, Masahiro Yamada wrote:

> Setting aside 2/2,
> 1/2 (this one) is apparently a bug fix and Matt reviewed it,
> so isn't it ready for v2016.08 ?

I don't understand why 1/2 is a bug fix. Could you clarify?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[Buildroot] [PATCH 1/2] zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG

[Masahiro Yamada]

Hi Thomas,

2016-08-10 21:58 GMT+09:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
> Hello,
>
> On Wed, 10 Aug 2016 21:31:16 +0900, Masahiro Yamada wrote:
>
>> Setting aside 2/2,
>> 1/2 (this one) is apparently a bug fix and Matt reviewed it,
>> so isn't it ready for v2016.08 ?
>
> I don't understand why 1/2 is a bug fix. Could you clarify?
>

"make uboot-menuconfig" does not work,
where it should work.



-- 
Best Regards
Masahiro Yamada

[Buildroot] [PATCH 1/2] zynq: enable BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG

[Peter Korsgaard]

>>>>> "Masahiro" == Masahiro Yamada <yamada.masahiro@socionext.com> writes:

 > The recent U-Boot adopts Kconfig for its configuration system.
 > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard