linux-rockchip.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: U-Boot-Denx <u-boot@lists.denx.de>,
	linux-amarula <linux-amarula@amarulasolutions.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH 07/11] env: Enable SPI flash env for rockchip
Date: Fri, 27 Dec 2019 12:20:24 +0530	[thread overview]
Message-ID: <CAMty3ZDQptk4NJkLfdGiygQMTdLNhSWOxNu57OOf-DpUhFndtA@mail.gmail.com> (raw)
In-Reply-To: <87672c9e-5f49-edf9-a97d-2ed83d33d375@rock-chips.com>

Hi Kever,

On Mon, Dec 23, 2019 at 8:04 AM Kever Yang <kever.yang@rock-chips.com> wrote:
>
> Jagan,
>
>
> On 2019/12/21 下午3:54, Jagan Teki wrote:
> > Most of the SPI flash devices in rockchip are 16MiB size.
> >
> > So, keeping U-Boot proper offset start from 128MiB with 1MiB
> > size and then start env of 8KiB would be a compatible location
> > between all variants of flash sizes.
> >
> > This patch add env start from 0x14000 with a size of 8KiB.
>
> What's the space map in SPI flash suppose to be? Including
> tpl/spl/u-boot.itb
>
> I would prefer to use 128KiB-8KiB as the env start address, we'd better
> to avoid the
>
> risk of overlap between the env space and the firmware space.

Here is the 16MiB flash layout, I have used. I can see the loader1
(tpl/spl) can be possible to load at 0x0 or 0x32K so I have given the
space for it. and 8K env after loader2(u-boot). let me know your
thoughts?

          0x0 - 0x8000,       32K  =>  reserved/loader1
    0x8000 - 0x40000,    224K =>  loader1
  0x40000 - 0x140000,    1M  =>  loader2
0x140000 - 0x142000,    8K  =>   env
0x142000 - 0x842000,    7M  =>  kernel
0x842000 - 0x853800,  100K =>  dtb
0x853800 -                             =>  root

Jagan.

  reply	other threads:[~2019-12-27  6:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21  7:54 [PATCH 00/11] rk3399: SPI boot support (fixes, updates) Jagan Teki
     [not found] ` <20191221075440.6944-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-21  7:54   ` [PATCH 01/11] spi: rk: Limit transfers to (64K - 1) bytes Jagan Teki
     [not found]     ` <20191221075440.6944-2-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-23  2:30       ` Kever Yang
2019-12-27  5:55         ` Jagan Teki
2019-12-21  7:54   ` [PATCH 02/11] distro_bootcmd: Add SF support Jagan Teki
2019-12-30  3:07     ` Kever Yang
2020-01-20 17:22     ` Tom Rini
2020-01-20 17:40       ` Alexander Graf
2020-01-23 16:55         ` Jagan Teki
2020-01-23 17:03           ` Tom Rini
2020-01-23 17:11             ` Jagan Teki
2020-01-23 17:15               ` Tom Rini
2020-01-23 17:29                 ` Jagan Teki
2020-01-23 17:59                   ` Tom Rini
2019-12-21  7:54   ` [PATCH 03/11] rockchip: Include SF on distrocmd devices Jagan Teki
     [not found]     ` <20191221075440.6944-4-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-30  3:07       ` Kever Yang
2020-01-07  8:44     ` Kever Yang
2019-12-21  7:54   ` [PATCH 04/11] rk3399: Add boot flash script offet, size Jagan Teki
2019-12-30  3:06     ` Kever Yang
2019-12-21  7:54   ` [PATCH 05/11] rk3399: Check MMC env while defining it Jagan Teki
2019-12-30  3:06     ` Kever Yang
2019-12-21  7:54   ` [PATCH 06/11] env: kconfig: Restrict rockchip env for MMC Jagan Teki
2019-12-30  3:05     ` Kever Yang
2019-12-21  7:54   ` [PATCH 07/11] env: Enable SPI flash env for rockchip Jagan Teki
2019-12-23  2:34     ` Kever Yang
2019-12-27  6:50       ` Jagan Teki [this message]
2019-12-27 10:02         ` Kever Yang
2019-12-27 10:10           ` Jagan Teki
2019-12-27 10:30         ` Soeren Moch
2019-12-27 12:04           ` Jagan Teki
2019-12-27 13:19             ` Soeren Moch
     [not found]               ` <30fdf54b-0f71-ffbf-ac57-51050a29b56d-S0/GAf8tV78@public.gmane.org>
2019-12-28 12:08                 ` Jagan Teki
2019-12-30  9:04                   ` Soeren Moch
2019-12-30  2:59     ` Kever Yang
2019-12-21  7:54   ` [PATCH 08/11] rockchip: dts: Sync ROC-RK3399-PC changes from Linux Jagan Teki
     [not found]     ` <20191221075440.6944-9-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-30  3:00       ` Kever Yang
2019-12-21  7:54   ` [PATCH 09/11] roc-pc-rk3399: Enable SPI Flash Jagan Teki
     [not found]     ` <20191221075440.6944-10-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-30  3:00       ` Kever Yang
2019-12-21  7:54   ` [PATCH 10/11] rockpro-rk3399: " Jagan Teki
2019-12-30  3:00     ` Kever Yang
     [not found]     ` <20191221075440.6944-11-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-30 11:51       ` Emmanuel Vadot
2020-01-08 12:59         ` Jagan Teki
2019-12-21  7:54   ` [PATCH 11/11] roc-rk3399-pc: Add SPI boot support Jagan Teki
2019-12-30  3:05     ` Kever Yang
2019-12-30  7:52       ` Jagan Teki
     [not found]         ` <CAMty3ZA1u3-21QN4N6W=9Sq3n493BBBB2W_FzAEQC9aze4SoMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-01-07  8:53           ` Kever Yang

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=CAMty3ZDQptk4NJkLfdGiygQMTdLNhSWOxNu57OOf-DpUhFndtA@mail.gmail.com \
    --to=jagan@amarulasolutions.com \
    --cc=kever.yang@rock-chips.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).