From mboxrd@z Thu Jan  1 00:00:00 1970
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
Date: Sun, 26 Apr 2020 22:21:19 +0200
Subject: [PATCH v2 6/7] x86: Add an indication of 32/64-bit to bdinfo
In-Reply-To: <20200426193824.171193-2-sjg@chromium.org>
References: <20200426193824.171193-1-sjg@chromium.org>
 <20200426193824.171193-2-sjg@chromium.org>
Message-ID: <77ab3c57-a320-b775-59f5-bd852bd7b782@gmx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 4/26/20 9:38 PM, Simon Glass wrote:
> It is useful to know what mode U-Boot is running in. Add a message at the
> end of the 'bdinfo' output.

X86 is not the only architecture that can run both in 32bit and 64bit
mode. The same is true for ARM and SANDBOX. Shouldn't we provide the
information for these architecture too?

The Raspberry Pi 3 is an example of an ARM board where building either
32bit or 64bit U-Boot is used depending on the bitness of the OS.

Best regards

Heinrich

>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v2:
> - Add a new patch to indicate 32/64-bit in bdinfo
>
>  cmd/bdinfo.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/cmd/bdinfo.c b/cmd/bdinfo.c
> index d6a7175b37..a3129c9fe1 100644
> --- a/cmd/bdinfo.c
> +++ b/cmd/bdinfo.c
> @@ -388,6 +388,7 @@ int do_bdinfo(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[])
>  	print_mhz("ethspeed",	    bd->bi_ethspeed);
>  #endif
>  	print_baudrate();
> +	printf("Build: %d-bit\n", CONFIG_IS_ENABLED(X86_64) ? 64 : 32);
>
>  	return 0;
>  }
>