All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] rockchip: rk3308: allow loading larger kernel Image
Date: Thu, 26 Dec 2019 20:25:05 +0800	[thread overview]
Message-ID: <f52b4d19-354f-b4c2-bc96-c4a5776fe810@rock-chips.com> (raw)
In-Reply-To: <20191226072004.8434-1-andy.yan@rock-chips.com>


On 2019/12/26 下午3:20, Andy Yan wrote:
> When compile the curren mainline linux kernel(Linux 5.5-rc3)
> with defconfig, the final Image is 29M, it's much
> larger than Linux 5.4.
>
> On the current u-boot side on rk3308, the gap between
> kernel and fdt is 25M, the fdt will overwrite kernel
> Image, so move ftd to a higher memory to give 34M
> gab for them.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>

Thanks,
- Kever
> ---
>
>   include/configs/rk3308_common.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/configs/rk3308_common.h b/include/configs/rk3308_common.h
> index a67d3d7d1b..bd9ac826f3 100644
> --- a/include/configs/rk3308_common.h
> +++ b/include/configs/rk3308_common.h
> @@ -42,7 +42,7 @@
>   #define ENV_MEM_LAYOUT_SETTINGS \
>   	"scriptaddr=0x00500000\0" \
>   	"pxefile_addr_r=0x00600000\0" \
> -	"fdt_addr_r=0x01f00000\0" \
> +	"fdt_addr_r=0x02800000\0" \
>   	"kernel_addr_r=0x00680000\0" \
>   	"ramdisk_addr_r=0x04000000\0"
>   

      parent reply	other threads:[~2019-12-26 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26  7:20 [PATCH 1/2] rockchip: rk3308: allow loading larger kernel Image Andy Yan
2019-12-26  7:20 ` [PATCH 2/2] doc: rockchip: Fix reference the wrong defconfig name of ROC-CC-RK3308 Andy Yan
2019-12-26 12:25   ` Kever Yang
2019-12-26 12:25 ` Kever Yang [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=f52b4d19-354f-b4c2-bc96-c4a5776fe810@rock-chips.com \
    --to=kever.yang@rock-chips.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 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.