From: Andrew Jones <andrew.jones@linux.dev>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 1/3] riscv: Add Image header to flat binaries
Date: Thu, 19 Dec 2024 09:27:23 +0100 [thread overview]
Message-ID: <20241219-d78dcb3804da755f52c2a8a3@orel> (raw)
In-Reply-To: <dbb66354-b08d-49f6-82a4-840be58bddb1@sifive.com>
On Wed, Dec 18, 2024 at 05:06:09PM -0600, Samuel Holland wrote:
> Hi Drew,
>
> On 2024-12-18 4:13 AM, Andrew Jones wrote:
> > On Mon, Dec 09, 2024 at 10:44:40PM -0600, Samuel Holland wrote:
> >> This allows flat binaries to be understood by U-Boot's booti command and
> >> its PXE boot flow.
> >>
> >> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
> >> ---
> >> riscv/cstart.S | 16 +++++++++++++++-
> >> 1 file changed, 15 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/riscv/cstart.S b/riscv/cstart.S
> >> index b7ee9b9c..106737a1 100644
> >> --- a/riscv/cstart.S
> >> +++ b/riscv/cstart.S
> >> @@ -39,15 +39,29 @@
> >> * The hartid of the current core is in a0
> >> * The address of the devicetree is in a1
> >> *
> >> - * See Linux kernel doc Documentation/riscv/boot.rst
> >> + * See Linux kernel doc Documentation/arch/riscv/boot.rst and
> >> + * Documentation/arch/riscv/boot-image-header.rst
> >> */
> >> .global start
> >> start:
> >> + j 1f
> >> + .balign 8
> >> + .dword 0 // text offset
> >
> > When I added a header like this for the bpi I needed the text offset to be
> > 0x200000, like Linux has it. Did you do something to avoid that?
>
> It turns out that U-Boot on my board is configured to ignore the first 0x200000
> bytes of DRAM entirely, so the binary ended up at the right address for the
> wrong reason. I can send a v2 with this field changed to 0x200000 (which also
> works on my board).
Sounds good.
Thanks,
drew
>
> Regards,
> Samuel
>
> >> + .dword stacktop - ImageBase // image size
> >> + .dword 0 // flags
> >> + .word (0 << 16 | 2 << 0) // version
> >> + .word 0 // res1
> >> + .dword 0 // res2
> >> + .ascii "RISCV\0\0\0" // magic
> >> + .ascii "RSC\x05" // magic2
> >> + .word 0 // res3
> >> +
> >> /*
> >> * Stash the hartid in scratch and shift the dtb address into a0.
> >> * thread_info_init() will later promote scratch to point at thread
> >> * local storage.
> >> */
> >> +1:
> >> csrw CSR_SSCRATCH, a0
> >> mv a0, a1
> >>
> >> --
> >> 2.39.3 (Apple Git-146)
> >>
> >
> > Thanks,
> > drew
>
next prev parent reply other threads:[~2024-12-19 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 4:44 [kvm-unit-tests PATCH 0/3] riscv: Improved bare metal support Samuel Holland
2024-12-10 4:44 ` [kvm-unit-tests PATCH 1/3] riscv: Add Image header to flat binaries Samuel Holland
2024-12-18 10:13 ` Andrew Jones
2024-12-18 23:06 ` Samuel Holland
2024-12-19 8:27 ` Andrew Jones [this message]
2025-03-22 9:18 ` Andrew Jones
2024-12-10 4:44 ` [kvm-unit-tests PATCH 2/3] riscv: Rate limit UART output to avoid FIFO overflows Samuel Holland
2024-12-10 4:44 ` [kvm-unit-tests PATCH 3/3] riscv: Support UARTs with different I/O widths Samuel Holland
2025-03-22 10:16 ` Andrew Jones
2024-12-18 10:06 ` [kvm-unit-tests PATCH 0/3] riscv: Improved bare metal support Andrew Jones
2025-03-22 9:16 ` [kvm-unit-tests PATCH 4/3] riscv: Support using SBI DBCN for the console Andrew Jones
2025-03-22 9:19 ` [kvm-unit-tests PATCH 0/3] riscv: Improved bare metal support Andrew Jones
2025-03-22 10:45 ` Andrew Jones
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=20241219-d78dcb3804da755f52c2a8a3@orel \
--to=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=samuel.holland@sifive.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