On Thu, 2 Jan 2020 16:52:50 +0100 (CET)
BALATON Zoltan wrote:
> On Thu, 2 Jan 2020, Igor Mammedov wrote:
> > On Wed, 1 Jan 2020 12:54:37 +0100 (CET)
> > BALATON Zoltan wrote:
> >> On Tue, 31 Dec 2019, Igor Mammedov wrote:
> >>> If user provided non-sense RAM size, board will complain and
> >
On Thu, 2 Jan 2020 16:52:50 +0100 (CET)
BALATON Zoltan wrote:
> On Thu, 2 Jan 2020, Igor Mammedov wrote:
> > On Wed, 1 Jan 2020 12:54:37 +0100 (CET)
> > BALATON Zoltan wrote:
> >> On Tue, 31 Dec 2019, Igor Mammedov wrote:
> >>> If user provided non-sense RAM size, board will complain and
> >
On Thu, 2 Jan 2020, Igor Mammedov wrote:
On Wed, 1 Jan 2020 12:54:37 +0100 (CET)
BALATON Zoltan wrote:
On Tue, 31 Dec 2019, 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 gener
On Wed, 1 Jan 2020 12:54:37 +0100 (CET)
BALATON Zoltan wrote:
> On Tue, 31 Dec 2019, 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
> > po
On Wed, 1 Jan 2020, Philippe Mathieu-Daudé wrote:
On 1/1/20 12:54 PM, BALATON Zoltan wrote:
On Tue, 31 Dec 2019, 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
On 1/1/20 12:54 PM, BALATON Zoltan wrote:
On Tue, 31 Dec 2019, 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
On Tue, 31 Dec 2019, 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 f
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-