From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Bin Meng <bmeng@tinylab.org>,
Alistair Francis <alistair.francis@wdc.com>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 09/10] board/sifive: hifive-unleashed: Update rootfs offset
Date: Mon, 26 Jun 2023 19:12:58 +0200 [thread overview]
Message-ID: <20230626171258.GF646621@scaer> (raw)
In-Reply-To: <20230626160030.93063-10-bmeng.cn@gmail.com>
Bin, All,
On 2023-06-27 00:00 +0800, Bin Meng spake thusly:
> From: Bin Meng <bmeng@tinylab.org>
>
> As the rootfs size is set to 60M, let's put it right on the 4M offset
> in the SD card, so that the generated sdcard.img can be exactly 64M.
As much I like power-of-two numbers, is there a technical reason to hit
exactly 64MiB?
Regards,
Yann E. MORIN.
> Signed-off-by: Bin Meng <bmeng@tinylab.org>
> ---
>
> board/sifive/hifive-unleashed/genimage_sdcard.cfg | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/board/sifive/hifive-unleashed/genimage_sdcard.cfg b/board/sifive/hifive-unleashed/genimage_sdcard.cfg
> index 079ac5ed26..99e3525a8c 100644
> --- a/board/sifive/hifive-unleashed/genimage_sdcard.cfg
> +++ b/board/sifive/hifive-unleashed/genimage_sdcard.cfg
> @@ -17,6 +17,7 @@ image sdcard.img {
>
> partition rootfs {
> image = "rootfs.ext4"
> + offset = 4076K
> partition-type-uuid = 0fc63daf-8483-4772-8e79-3d69d8477de4
> bootable = true
> }
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@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@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-26 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 16:00 [Buildroot] [PATCH 00/10] riscv: Various fixes and small enhancements Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 01/10] configs/hifive_unleashed: Update to use OpenSBI 1.2 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 02/10] configs/hifive_unleashed: Update to use U-Boot v2023.04 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 03/10] configs/hifive_unleashed: Enable BR2_RISCV_ISA_CUSTOM_RVA explicitly Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 04/10] configs/beaglev_defconfig: " Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 05/10] arch/Config.in.riscv: Remove BR2_RISCV_ISA_CUSTOM_RVA from BR2_riscv_custom Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 06/10] configs: riscv: Drop BR2_TARGET_OPENSBI_CUSTOM_VERSION Bin Meng
2023-06-26 17:10 ` Yann E. MORIN
2023-06-27 2:11 ` Bin Meng
2023-06-27 20:39 ` Yann E. MORIN
2023-06-26 16:00 ` [Buildroot] [PATCH 07/10] boot/opensbi: Config.in: Cosmetic style fix Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 08/10] boot/opensbi: Bump to version 1.3 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 09/10] board/sifive: hifive-unleashed: Update rootfs offset Bin Meng
2023-06-26 17:12 ` Yann E. MORIN [this message]
2023-08-12 21:12 ` Thomas Petazzoni via buildroot
2023-06-26 16:00 ` [Buildroot] [PATCH 10/10] board/sifive: hifive-unleashed: Include QEMU instructions in readme.txt Bin Meng
2023-06-26 17:21 ` Yann E. MORIN
2023-06-27 0:32 ` Alistair Francis
2023-06-28 15:15 ` Bin Meng
2023-08-12 21:14 ` Thomas Petazzoni via buildroot
2023-06-26 17:04 ` [Buildroot] [PATCH 00/10] riscv: Various fixes and small enhancements Yann E. MORIN
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=20230626171258.GF646621@scaer \
--to=yann.morin.1998@free.fr \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=bmeng@tinylab.org \
--cc=buildroot@buildroot.org \
--cc=jbglaw@lug-owl.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