public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [SPL mode] Question
Date: Thu, 15 Nov 2012 16:51:37 +0100	[thread overview]
Message-ID: <20121115165137.79ee71a6@amdc308.digital.local> (raw)

Hi Stefano,

I've got some questions about Falcon mode and spl export command.

I've looked into the ./common/cmd_spl.c at master branch
SHA1: 59852d03867108217fe88e3bfc3e1e9cedfe63c5

Correct me if I'm wrong (or I've overlooked something). 
It looks that, this file version is a very early version. 

After reading "Falcon" mode README - I'd expect, that "spl export" will
write either ATAGS or FDT to NAND (or any other memory).
For this file it doesn't do that. Am I missing some additional patches?

Since you stated, that Falcon mode is only (now) supported on NAND
memory, I'd like to ask if it is acceptable to extend cmd_spl.c to
write ATAGS/FDT image to eMMC or (better) to partition formatted as EXT4
of FAT?

I can imagine a following scenario:

1. Use u-boot to generate ATAGS (from bootcmd args defined for board
or cmd line parameters) or FDT blob with "spl export". Store it on a
partition or eMMC.

2. Use SPL (second stage bootloader) to parse this blob, place ATAGS or
FDT accordingly, read uImage and pass execution to it.

What is your opinion?


-- 
Best regards,

Lukasz Majewski

Samsung Poland R&D Center | Linux Platform Group

             reply	other threads:[~2012-11-15 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 15:51 Lukasz Majewski [this message]
2012-11-15 16:32 ` [U-Boot] [SPL mode] Question Andreas Bießmann
2012-11-16 10:59   ` Lukasz Majewski
2012-11-15 16:43 ` Stefano Babic

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=20121115165137.79ee71a6@amdc308.digital.local \
    --to=l.majewski@samsung.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