From: Mattia Narducci <mattianarducci1@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] configs/pine64: bump U-Boot version to 2024.07
Date: Wed, 04 Sep 2024 21:54:37 +0200 [thread overview]
Message-ID: <4949491.31r3eYUQgx@localhost> (raw)
In-Reply-To: <20240903215308.27bb1d2c@windsurf>
On Tue, 03 Sep 2024 21:53:08 CEST Thomas Petazzoni wrote:
> On Sun, 01 Sep 2024 18:42:58 +0200
> Mattia Narducci <mattianarducci1@gmail.com> wrote:
> > partition u-boot {
> > in-partition-table = "no"
> > - image = "u-boot.itb"
> > - offset = 40K
> > - size = 1M # 1MB - 40KB
> > + image = "u-boot-sunxi-with-spl.bin"
> > + offset = 8K
> > + size = 1016K # 1MB - 8KB
>
> Here this "size" field is a bit silly. We don't really care that the
> size is 1016KB. What we care is that the offset is 8 KB, and that the
> next partition is aligned on a good boundary.
>
> So could you test something like:
>
> https://patchwork.ozlabs.org/project/buildroot/patch/tencent_92439641515553684D208B3331676FB36C05@qq.com/
>
> instead?
Sure! I have seen this approach used for other boards and thought it
was fine, but the offset is definitely clearer.
--
Mattia
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-04 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 16:42 [Buildroot] [PATCH 1/3] configs/pine64: bump U-Boot version to 2024.07 Mattia Narducci
2024-09-01 16:44 ` [Buildroot] [PATCH 2/3] configs/pine64: bump TF-A version to 2.10.5 Mattia Narducci
2024-09-01 16:46 ` [Buildroot] [PATCH 3/3] configs/pine64: bump Linux to version 6.6.48 Mattia Narducci
2024-09-03 19:53 ` [Buildroot] [PATCH 1/3] configs/pine64: bump U-Boot version to 2024.07 Thomas Petazzoni via buildroot
2024-09-04 19:54 ` Mattia Narducci [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=4949491.31r3eYUQgx@localhost \
--to=mattianarducci1@gmail.com \
--cc=buildroot@buildroot.org \
--cc=jagan@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.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.