public inbox for opensbi@lists.infradead.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: opensbi@lists.infradead.org
Subject: Invalid build with change in PLATFORM and no clean
Date: Wed, 17 Sep 2025 02:22:59 -0700	[thread overview]
Message-ID: <10b584c6-9fd8-4b4f-a114-2b96a9073d20@freeshell.de> (raw)

Hello,

I have narrowed down a strange behavior from U-Boot which may be worth
sharing, related to OpenSBI.

Steps to reproduce:

1. (OpenSBI) checkout opensbi v1.7

2. (OpenSBI) make

3. (OpenSBI) make PLATFORM=generic

when U-Boot v2025.10-rc4 links to opensbi:
4. (U-Boot) make starfive_visionfive2_defconfig:
5. (U-Boot) make OPENSBI=/path/to/fw_payload.bin

the result of U-Boot `reset` command is:

StarFive # reset

resetting ...

System reset not supported on this platform

### ERROR ### Please RESET the board ###

6. (OpenSBI) make PLATFORM=generic clean ; make PLATFORM=generic

7. (U-Boot) make OPENSBI=/path/to/fw_payload.bin

result of U-Boot `reset` command is normal, system resets and does not
complain.

Can this be improved in the OpenSBI build system?  It is difficult to
figure out that OpenSBI needs a make clean from the symptom;  I thought
that it might be some devicetree property or unknown in U-Boot, but
after hours trying to git bisect U-Boot that was not it at all, it's the
dependency tracking in OpenSBI build system not catching the change in
PLATFORM.

Best regards,

-E Shattow (not on the list please CC/reply-all thank you!)

-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

             reply	other threads:[~2025-09-17  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  9:22 E Shattow [this message]
2025-09-17 16:40 ` Invalid build with change in PLATFORM and no clean Samuel Holland

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=10b584c6-9fd8-4b4f-a114-2b96a9073d20@freeshell.de \
    --to=e@freeshell.de \
    --cc=opensbi@lists.infradead.org \
    /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