All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dagg Stompler <daggs@gmx.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/ordeidc2: increase image size to 256M
Date: Sat, 11 Sep 2021 11:27:13 +0200	[thread overview]
Message-ID: <20210911092713.GI1053080@scaer> (raw)
In-Reply-To: <20210911084204.22150-1-daggs@gmx.com>

Dagg, All,

On 2021-09-11 11:42 +0300, Dagg Stompler spake thusly:
> following Commit 9f127cc4, the resulting image is bigger than possible.

I fail to see how commit 9f127cc4 can be the culprit:

    9f127cc4 utils/getdeveloperlib.py: explicitly set devs document encoding

> so BR2_TARGET_ROOTFS_EXT2_SIZE set to 256M is required.

The default is 60M; bumping to 256M is surely a big jump. Can't we
settle for something smaller, like 128M?

Also, note that the default is 60M, as we consider a 64M SDCard, and
thus some space is reserved at the begining for the boot blobs; see
board/hardkernel/odroidc2/genimage.cfg

And as a consequence, the size of the SDCard must also be updated in
board/hardkernel/odroidc2/genimage.cfg.

So, maybe:
  - update board/hardkernel/odroidc2/genimage.cfg from 64M to 128M
  - update BR2_TARGET_ROOTFS_EXT2_SIZE to 124M

Regards,
Yann E. MORIN.

> Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/1575071376
> 
> Signed-off-by: Dagg Stompler <daggs@gmx.com>
> ---
>  configs/odroidc2_defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configs/odroidc2_defconfig b/configs/odroidc2_defconfig
> index 5f97fc3dd8..daa818e036 100644
> --- a/configs/odroidc2_defconfig
> +++ b/configs/odroidc2_defconfig
> @@ -10,6 +10,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttyAML0"
>  BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200=y
>  BR2_TARGET_ROOTFS_EXT2=y
>  BR2_TARGET_ROOTFS_EXT2_4=y
> +BR2_TARGET_ROOTFS_EXT2_SIZE="256M"
>  BR2_ROOTFS_OVERLAY="board/hardkernel/odroidc2/rootfs_overlay"
>  BR2_ROOTFS_POST_IMAGE_SCRIPT="board/hardkernel/odroidc2/post-image.sh"
> 
> --
> 2.33.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@lists.buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-09-11  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11  8:42 [Buildroot] [PATCH] configs/ordeidc2: increase image size to 256M Dagg Stompler
2021-09-11  9:27 ` Yann E. MORIN [this message]
2021-09-11  9:30   ` Yann E. MORIN
2021-09-11 14:30     ` daggs
2021-09-11 14:29   ` daggs
2021-09-11 15:23     ` Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2021-09-11  8:37 Dagg Stompler

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=20210911092713.GI1053080@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=daggs@gmx.com \
    /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.