From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
"open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>,
Akash Gajjar <akash@openedev.com>,
linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH v5 7/7] doc: boards: Add rockchip documentation
Date: Tue, 31 Dec 2019 10:50:42 +0300 [thread overview]
Message-ID: <CAJs94EacaLU4QJkhKAm6+v_=rtyNWkeCoYONLF43qTVSCko-cw@mail.gmail.com> (raw)
In-Reply-To: <CAMty3ZDkaVCBmKeofqn7p+EVGdHx3NZDt13kN6Nx_WVFSF5Pyg@mail.gmail.com>
пн, 30 дек. 2019 г. в 11:59, Jagan Teki <jagan@amarulasolutions.com>:
>
> Hi,
>
> On Mon, Dec 30, 2019 at 2:11 PM Matwey V. Kornilov
> <matwey.kornilov@gmail.com> wrote:
> >
> > Hello,
> >
> > Thank you for the patch set.
> > Currently, I have the following concern about documentation and
> > overall proposed u-boot deploy procedure.
> >
> > There is a use case, when I have to use Rockchip proprietary TPL
> > binary and deploy it instead of u-boot's one together with u-boot SPL
> > and ITB images.
> > It is required for debugging purposes because unfortunately u-boot TPL
> > is usually less stable that proprietary one. And switching the TPL
> > binary is basically the first step when I see random strange crashes.
> > It is a good way to locate an issue origin.
> >
> > Could we somehow ensure that this backup deployment plan is still
> > possible and documented in the text here? It would be great if the
> > user could learn the procedure from the text, not from the source
> > code, recovering correct offsets.
>
> You mean to say rkbin => SPL => U-Boot proper ? if yes, I do agree
Yes, I mean so.
I think it would be great to have something like the section
describing where do the things came from and the layout which is under
the hood.
> with this point and it is worth to document it as well. Kever, will
> that be okay for you?
>
> Jagan.
--
With best regards,
Matwey V. Kornilov
prev parent reply other threads:[~2019-12-31 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 8:28 [PATCH v5 0/7] rockchip: Add Binman support Jagan Teki
[not found] ` <20191230082819.30191-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-30 8:28 ` [PATCH v5 1/7] Makefile: Add rockchip image type Jagan Teki
2019-12-30 8:28 ` [PATCH v5 2/7] Makefile: rockchip: Suffix platform type with tpl name Jagan Teki
2019-12-30 8:28 ` [PATCH v5 3/7] Makefile: rockchip: Support SPL-alone mkimage Jagan Teki
2019-12-30 8:28 ` [PATCH v5 4/7] Makefile: rockchip: Use u-boot preferred spl name Jagan Teki
2019-12-30 8:28 ` [PATCH v5 5/7] arm: dts: rk3036: Add rk3036-u-boot.dtsi Jagan Teki
2019-12-30 8:28 ` [PATCH v5 6/7] rockchip: Add Single boot image (with binman, pad_cat) Jagan Teki
2019-12-31 7:54 ` Matwey V. Kornilov
2019-12-31 8:04 ` Matwey V. Kornilov
[not found] ` <CAJs94EZgpHmkHAfDQUH_mqW82Jw_QJWiJgx_8Uny1ru1WfbrHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-01-03 17:35 ` Jagan Teki
2019-12-30 8:28 ` [PATCH v5 7/7] doc: boards: Add rockchip documentation Jagan Teki
2019-12-30 8:41 ` Matwey V. Kornilov
[not found] ` <CAJs94EYBrwf9Pt0R-_OypT-JHWGFpZYxRhKcUXWgXTFJi9O0HA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-12-30 8:59 ` Jagan Teki
2019-12-31 7:50 ` Matwey V. Kornilov [this message]
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='CAJs94EacaLU4QJkhKAm6+v_=rtyNWkeCoYONLF43qTVSCko-cw@mail.gmail.com' \
--to=matwey.kornilov@gmail.com \
--cc=akash@openedev.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-rockchip@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).