From: Tom Rini <trini@konsulko.com>
To: Nathan Barrett-Morrison <nathan.morrison@timesys.com>
Cc: u-boot@lists.denx.de
Subject: Re: Falcon Mode Support For Uncompressed Kernel Images
Date: Mon, 31 Jan 2022 10:35:54 -0500 [thread overview]
Message-ID: <20220131153554.GV7515@bill-the-cat> (raw)
In-Reply-To: <CAPE2wM0Dbq5yEssC1AMFy=d+rhO-EgxpoA-v3w+5n4ooCW9P+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Mon, Jan 31, 2022 at 10:23:58AM -0500, Nathan Barrett-Morrison wrote:
> Hi Tom,
>
> Yea, I'm not sure if uncompressed ARM32 would work, but I don't believe it
> was ever working to begin with... as bootz_setup is being called right now
> ( @ https://source.denx.de/u-boot/u-boot/-/blob/master/common/spl/spl.c#L366
> )
>
> My intent was for SPL_OS_BOOT_UNCOMPRESSED to only be used for platforms
> which need booti_setup (ARM64, ...).
>
> So... I could add a dependency on ARM64 in the config option or I could
> remove the option altogether and let the booti_setup fail and fallback to
> bootz_setup. Would either of those work for you?
The code and logic overall needs a bit of refactoring to support
"booti", "bootz" and also FIT images. I believe FIT images are how
anyone doing falcon mode on arm64 has worked thus far. booti/bootz
should only be an option when CMD_BOOTI/Z is set, and FIT should depend
on SPL_LOAD_FIT already.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-31 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 0:58 Falcon Mode Support For Uncompressed Kernel Images Nathan Barrett-Morrison
2022-01-31 15:11 ` Tom Rini
2022-01-31 15:23 ` Nathan Barrett-Morrison
2022-01-31 15:35 ` Tom Rini [this message]
2022-02-02 21:53 ` Nathan Barrett-Morrison
2022-04-19 20:30 ` Tom Rini
2022-04-19 21:16 ` Nathan Barrett-Morrison
2022-04-19 21:20 ` Nathan Barrett-Morrison
2022-04-19 21:28 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2022-04-19 21:31 Nathan Barrett-Morrison
2022-04-19 21:36 ` Tom Rini
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=20220131153554.GV7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=nathan.morrison@timesys.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