From: Wadim Egorov <w.egorov@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 8/8] doc: Add RK3288 Documentation
Date: Thu, 21 Jul 2016 09:09:36 +0200 [thread overview]
Message-ID: <57907530.1070805@phytec.de> (raw)
In-Reply-To: <20160721070048.GU20657@pengutronix.de>
On 21.07.2016 09:00, Sascha Hauer wrote:
> On Wed, Jul 20, 2016 at 04:17:45PM +0200, Wadim Egorov wrote:
>> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
>> ---
>> Documentation/boards/rk3288.rst | 57 ++++++++++++++++++++++++++++++
>> Documentation/boards/rk3288/phytec-som.rst | 24 +++++++++++++
>> 2 files changed, 81 insertions(+)
>> create mode 100644 Documentation/boards/rk3288.rst
>> create mode 100644 Documentation/boards/rk3288/phytec-som.rst
>>
>> diff --git a/Documentation/boards/rk3288.rst b/Documentation/boards/rk3288.rst
>> new file mode 100644
>> index 0000000..3acca74
>> --- /dev/null
>> +++ b/Documentation/boards/rk3288.rst
>> @@ -0,0 +1,57 @@
>> +Rockchip RK3288
>> +===============
>> +
>> +The RK3288 SoC has a two stage boot process. The booting is completed in two
>> +consecutive stages. The binary for the 1st stage is referred to as the
>> +Secondary Program Loader (SPL). The binary for the 2nd stage is simply referred to
>> +as barebox.
>> +SPL is a non-interactive loader and is only used to boot the 2nd stage loader.
>> +
>> +At this moment barebox can only be used as a 2nd stage bootloader.
>> +Starting barebox requires another bootloader which will do the very basic
>> +SDRAM initialization for us. We can use the u-boot for that.
> Do you plan to add SPL support for barebox aswell? From what I see in
> the U-Boot source code the Rockchip SoCs seem to be of the nicer SoCs
> which do not require that much and complicated setup.
>
> Sascha
Yes, I would like to add SPL support for barebox later.
The only problem I see is the very limited SPL size (32K).
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-07-21 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 14:17 [PATCH 1/8] ARM: rockchip: Add basic RK3288 support Wadim Egorov
2016-07-20 14:17 ` [PATCH 2/8] ARM: rockchip: Add timer driver Wadim Egorov
2016-07-20 17:35 ` Andrey Smirnov
2016-07-28 11:55 ` Wadim Egorov
2016-07-28 19:12 ` Andrey Smirnov
2016-08-03 5:47 ` Sascha Hauer
2016-08-03 6:59 ` Wadim Egorov
2016-07-20 14:17 ` [PATCH 3/8] ARM: rockchip: Add early debug support for RK3288 Wadim Egorov
2016-07-20 15:03 ` Andrey Smirnov
2016-07-28 11:52 ` Wadim Egorov
2016-07-28 18:55 ` Andrey Smirnov
2016-07-20 14:17 ` [PATCH 4/8] clk: Add RK3288 clock driver Wadim Egorov
2016-07-20 14:17 ` [PATCH 5/8] mci: dw_mmc: Add RK3288 compatible string Wadim Egorov
2016-07-20 14:17 ` [PATCH 6/8] ARM: Add phyCORE-RK3288 SOM support Wadim Egorov
2016-07-20 17:57 ` Andrey Smirnov
2016-07-20 14:17 ` [PATCH 7/8] configs: Add RK3288 defconfig Wadim Egorov
2016-07-20 14:17 ` [PATCH 8/8] doc: Add RK3288 Documentation Wadim Egorov
2016-07-21 7:00 ` Sascha Hauer
2016-07-21 7:09 ` Wadim Egorov [this message]
2016-07-20 17:52 ` [PATCH 1/8] ARM: rockchip: Add basic RK3288 support Andrey Smirnov
2016-07-21 6:54 ` Sascha Hauer
2016-07-28 11:59 ` Wadim Egorov
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=57907530.1070805@phytec.de \
--to=w.egorov@phytec.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.