Re: [PATCH v5 34/79] arm/xilinx_zynq: drop RAM size fixup

2020-02-19 Thread Philippe Mathieu-Daudé
On 2/19/20 2:44 PM, Igor Mammedov wrote: On Tue, 18 Feb 2020 18:23:47 +0100 Philippe Mathieu-Daudé wrote: On 2/17/20 6:34 PM, Igor Mammedov wrote: If user provided non-sense RAM size, board will complain and continue running with max RAM size supported. Also RAM is going to be allocated by ge

Re: [PATCH v5 34/79] arm/xilinx_zynq: drop RAM size fixup

2020-02-19 Thread Igor Mammedov
On Tue, 18 Feb 2020 18:23:47 +0100 Philippe Mathieu-Daudé wrote: > On 2/17/20 6:34 PM, Igor Mammedov wrote: > > If user provided non-sense RAM size, board will complain and > > continue running with max RAM size supported. > > Also RAM is going to be allocated by generic code, so it won't be > >

Re: [PATCH v5 34/79] arm/xilinx_zynq: drop RAM size fixup

2020-02-18 Thread Philippe Mathieu-Daudé
On 2/17/20 6:34 PM, Igor Mammedov wrote: If user provided non-sense RAM size, board will complain and continue running with max RAM size supported. Also RAM is going to be allocated by generic code, so it won't be possible for board to fix things up for user. Make it error message and exit to fo

Re: [PATCH v5 34/79] arm/xilinx_zynq: drop RAM size fixup

2020-02-17 Thread Richard Henderson
On 2/17/20 9:34 AM, Igor Mammedov wrote: > If user provided non-sense RAM size, board will complain and > continue running with max RAM size supported. > Also RAM is going to be allocated by generic code, so it won't be > possible for board to fix things up for user. > > Make it error message and

[PATCH v5 34/79] arm/xilinx_zynq: drop RAM size fixup

2020-02-17 Thread Igor Mammedov
If user provided non-sense RAM size, board will complain and continue running with max RAM size supported. Also RAM is going to be allocated by generic code, so it won't be possible for board to fix things up for user. Make it error message and exit to force user fix CLI, instead of accepting non-