From: "Milan P. Stanić" <mps@arvanta.net>
To: Nam Cao <namcao@linutronix.de>
Cc: ycliang@andestech.com, yanhong.wang@starfivetech.com,
chanho61.park@samsung.com, wiagn233@outlook.com,
sjg@chromium.org, inindev@gmail.com, rick@andestech.com,
bmeng@tinylab.org, u-boot@lists.denx.de,
minda.chen@starfivetech.com
Subject: Re: [PATCH] starfive: visionfive2: switch to standard boot
Date: Mon, 18 Mar 2024 21:34:31 +0100 [thread overview]
Message-ID: <20240318203431.GA21567@m1pro.arvanta.net> (raw)
In-Reply-To: <20240314130436.76a2892a@namcao>
On Thu, 2024-03-14 at 13:04, Nam Cao wrote:
> On 13/Mar/2024 Milan P. Stanić wrote:
> > On Wed, 2024-02-21 at 13:00, Nam Cao wrote:
> > > Distro boot scripts are deprecated. Use standard boot instead.
> > I had to enable 'CONFIG_CMD_SYSBOOT=y' in
> > configs/starfive_visionfive2_defconfig because it doesn't boot without
> > it. With this option it boots fine with this patch.
>
> You should not have to do that for it to work, otherwise this patch
> introduced a bug.
>
> CONFIG_CMD_SYSBOOT adds the "sysboot" command, which is only used by
> distroboot. So I suspect that you were actually still using distro boot,
> because you didn't "update" your environment variable (that can be checked
> with "printenv bootcmd"). For this patch to work, the environment variables
> also need to be updated with:
> env default
> env save -a
>
> This makes me realize that the patch breaks boards if the users forget to
> update the environment variables. I am not sure if this is considered a
> bug. What do maintainers think?
Rebuild it again and it worked out of the box.
Tested-by: Milan P. Stanić <mps@arvanta.net>
next prev parent reply other threads:[~2024-03-18 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 12:00 [PATCH] starfive: visionfive2: switch to standard boot Nam Cao
2024-03-12 6:31 ` Leo Liang
2024-03-13 18:42 ` Milan P. Stanić
2024-03-14 12:04 ` Nam Cao
2024-03-18 20:34 ` Milan P. Stanić [this message]
2024-03-28 5:02 ` E Shattow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240318203431.GA21567@m1pro.arvanta.net \
--to=mps@arvanta.net \
--cc=bmeng@tinylab.org \
--cc=chanho61.park@samsung.com \
--cc=inindev@gmail.com \
--cc=minda.chen@starfivetech.com \
--cc=namcao@linutronix.de \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=wiagn233@outlook.com \
--cc=yanhong.wang@starfivetech.com \
--cc=ycliang@andestech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox