Hi Angelo,
On 05/09/18 05:41, Angelo Dureghello wrote:
please drop this patch.
Issue is not related to additional spaces in the command
line, nor to init.data initializaitons.
It seems qiute hard to track down, issue disappears if i
just add some lines of code in uboot.c or setup.c.
Thanks
Hi Greg,
please drop this patch.
Issue is not related to additional spaces in the command
line, nor to init.data initializaitons.
It seems qiute hard to track down, issue disappears if i
just add some lines of code in uboot.c or setup.c.
Continuing on this.
Regards,
Angelo Dureghello
On
Hi Geert,
On Sat, Sep 01, 2018 at 09:23:42AM +0200, Geert Uytterhoeven wrote:
> Hi Angelo,
>
> On Sat, Sep 1, 2018 at 3:17 AM Angelo Dureghello wrote:
> > Without MMU, when CONFIG_UBOOT is set, and CONFIG_BOOTPARAM
> > is not set, a wrong command-line was produced (boot hangs,
> > no console),
Hi Angelo,
On Sat, Sep 1, 2018 at 3:17 AM Angelo Dureghello wrote:
> Without MMU, when CONFIG_UBOOT is set, and CONFIG_BOOTPARAM
> is not set, a wrong command-line was produced (boot hangs,
> no console), due to an initial erroneus space appended to the
> command line in
