From: Harrison Mutai <harrison.mutai@arm.com>
To: Simon Glass <sjg@chromium.org>
Cc: Liviu Dudau <liviu.dudau@foss.arm.com>,
Tom Rini <trini@konsulko.com>,
nd@arm.com, andre.przywara@arm.com, manish.pandey2@arm.com,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 2/4] board: vexpress64: default to hardware device tree
Date: Thu, 16 Jan 2025 11:20:47 +0000 [thread overview]
Message-ID: <acbadc6f-9e1d-47e6-b3de-d7bf47a4e14d@arm.com> (raw)
In-Reply-To: <CAFLszTjS2mY1FrWM9dLAwOZ1soiOBP6GgMOYWwYQP6XPw9L9EA@mail.gmail.com>
Hi Simon,
On 16/01/2025 01:26, Simon Glass wrote:
> Hi Harrison,
>
> On Wed, 15 Jan 2025 at 06:52, Harrison Mutai <harrison.mutai@arm.com> wrote:
>>
>> When booting into the Linux kernel with semi-hosting, use the device
>> tree provided by hardware unless one is provided in the current
>> directory.
>>
>> Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
>> ---
>> include/configs/vexpress_aemv8.h | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>
> Thinking about standard boot, could we add a bootdev for hostfs? Then
> we could drop these scripts.
>
I have a patch in progress to migrate vexpress64 to standard boot that
tries to do this. However, it's not quite ready for upstreaming. For
one, there's other boot targets in this file that would need similar
treatment (e.g., AFS, MEM). Would it be possible to transition these in
a piece-wise manner?
>> diff --git a/include/configs/vexpress_aemv8.h b/include/configs/vexpress_aemv8.h
>> index 8020689e39..2341b3a938 100644
>> --- a/include/configs/vexpress_aemv8.h
>> +++ b/include/configs/vexpress_aemv8.h
>> @@ -169,12 +169,14 @@
>> " if load hostfs - ${kernel_addr_r} ${kernel_name}; then" \
>> " setenv fdt_high 0xffffffffffffffff;" \
>> " setenv initrd_high 0xffffffffffffffff;" \
>> - " load hostfs - ${fdt_addr_r} ${fdtfile};" \
>> + " if test -n load hostfs - ${fdt_addr_r} ${fdtfile}; then" \
>> + " fdt move $fdtcontroladdr $fdt_addr_r;" \
>> + " fi;" \
>> " load hostfs - ${ramdisk_addr_r} ${ramdisk_name};" \
>> " fdt addr ${fdt_addr_r};" \
>> " fdt resize;" \
>> " fdt chosen ${ramdisk_addr_r} ${filesize};" \
>> - " booti $kernel_addr_r - $fdt_addr_r;" \
>> + " booti $kernel_addr_r - ${fdt_addr_r};" \
>> " fi;" \
>> "fi\0"
>> #define BOOTENV_DEV_NAME_SMH(devtypeu, devtypel, instance) "smh "
>> --
>> 2.46.2
>>
>
> Regards,
> Simon
All the best,
Harrison
next prev parent reply other threads:[~2025-01-16 11:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 13:52 [PATCH v2 0/4] Enable bloblist support on Vexpress64 Harrison Mutai
2025-01-15 13:52 ` [PATCH v2 1/4] bloblist: fix typo in code comments Harrison Mutai
2025-01-15 14:35 ` Tom Rini
2025-01-15 13:52 ` [PATCH v2 2/4] board: vexpress64: default to hardware device tree Harrison Mutai
2025-01-16 1:26 ` Simon Glass
2025-01-16 11:20 ` Harrison Mutai [this message]
2025-01-16 11:33 ` Harrison Mutai
2025-01-15 13:52 ` [PATCH v2 3/4] bloblist: add support for CONFIG_BLOBLIST_PASSAGE Harrison Mutai
2025-01-15 14:36 ` Tom Rini
2025-01-16 1:26 ` Simon Glass
2025-01-22 17:21 ` Tom Rini
2025-01-23 17:03 ` Harrison Mutai
2025-01-23 17:12 ` Tom Rini
2025-01-27 12:42 ` Harrison Mutai
2025-01-31 0:10 ` Tom Rini
2025-02-03 12:28 ` Harrison Mutai
2025-02-03 22:22 ` Tom Rini
2025-02-04 10:32 ` Harrison Mutai
2025-01-15 13:52 ` [PATCH v2 4/4] board: vexpress64: enable bloblist for SPL handoff Harrison Mutai
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=acbadc6f-9e1d-47e6-b3de-d7bf47a4e14d@arm.com \
--to=harrison.mutai@arm.com \
--cc=andre.przywara@arm.com \
--cc=liviu.dudau@foss.arm.com \
--cc=manish.pandey2@arm.com \
--cc=nd@arm.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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