From: "Alex G." <mr.nuke.me@gmail.com>
To: Chan Kim <ckim@etri.re.kr>, U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: a question about falcon mode
Date: Thu, 25 Nov 2021 08:57:07 -0600 [thread overview]
Message-ID: <27ce6d77-2a3e-a9e2-cce2-00f76d7af57e@gmail.com> (raw)
In-Reply-To: <027001d7e1cb$14bc3b90$3e34b2b0$@etri.re.kr>
On 11/25/21 1:07 AM, Chan Kim wrote:
> Hello all,
>
> I'm trying to implement falcon mode for our board. Then should I first
> implement the normal mode(spl + proper)?
>
> It looks like so while I'm reading doc/README.falcon. (It says, after
> loading kernel, DT etc. I should give 'spl export' command).
>
Falcon mode is a bit board dependent. There are a couple of ways you
could go about this.
The first is to have an "fdtargs" partition. This is where "spl export"
comes in. Once you run "spl export", it will give a modified dtb at
"$fdtargsaddr". It's that DTB that you need to write to your ftdargs
partition. For example:
> spl export fdt $loadaddr - $fdt_addr_r
> mmc write $fdtargsaddr 0x9800 0x8000
In this example the ftdargs partition starts at sector 0x9800, and is
0x800 sectors long.
The second option is to forget about "spl export" and "fdtargs", and
package your kernel, devicetree, and overlays in a FIT container. You'd
make sure to enable SPL_LOAD_FIT_APPLY_OVERLAY. There isn't much more to
this other than the usual gotcha's with FIT and overlays.
Alex
next prev parent reply other threads:[~2021-11-25 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 7:07 a question about falcon mode Chan Kim
2021-11-25 14:57 ` Alex G. [this message]
2021-11-26 7:53 ` Chan Kim
2021-11-26 14:18 ` Alex G.
2021-11-26 22:36 ` Abder
2021-11-29 22:12 ` Alex G.
2021-12-01 12:16 ` Abder
2021-12-03 9:12 ` Chan Kim
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=27ce6d77-2a3e-a9e2-cce2-00f76d7af57e@gmail.com \
--to=mr.nuke.me@gmail.com \
--cc=ckim@etri.re.kr \
--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