From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Mattia Narducci <mattianarducci1@gmail.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: Tue, 3 Sep 2024 21:53:08 +0200 [thread overview]
Message-ID: <20240903215308.27bb1d2c@windsurf> (raw)
In-Reply-To: <1913421.tdWV9SEqCh@localhost>
On Sun, 01 Sep 2024 18:42:58 +0200
Mattia Narducci <mattianarducci1@gmail.com> wrote:
> Update U-Boot to fix the following error when building with
> python-setuptools >= 69, that is, since 6b62384e3d
> ("package/python-setuptools: bump to version 69.0.3"):
>
> packaging.version.InvalidVersion: Invalid version: 'u-boot-2019.01'
> make[5]: *** [scripts/dtc/pylibfdt/Makefile:27: scripts/dtc/pylibfdt/_libfdt.so] Error 1
> make[4]: *** [scripts/Makefile.build:434: scripts/dtc/pylibfdt] Error 2
> make[4]: *** Waiting for unfinished jobs....
> make[3]: *** [scripts/Makefile.build:434: scripts/dtc] Error 2
> make[2]: *** [Makefile:508: scripts] Error 2
> make[1]: *** [package/pkg-generic.mk:289: output/build/uboot-2019.01/.stamp_built] Error 2
> make: *** [Makefile:83: _all] Error 2
>
> Use SPL and U-Boot FIT image combined into u-boot-sunxi-with-spl.bin.
>
> Do not use the optional System Control Processor (SCP) firmware pointing
> the SCP env variable to /dev/null.
>
> Signed-off-by: Mattia Narducci <mattianarducci1@gmail.com>
> ---
> board/pine64/pine64/genimage.cfg | 12 +++---------
> configs/pine64_defconfig | 8 ++++----
> 2 files changed, 7 insertions(+), 13 deletions(-)
Series applied to next. However, if possible I'd like you to test/send
a follow-up patch.
> 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?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-03 19:53 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 ` Thomas Petazzoni via buildroot [this message]
2024-09-04 19:54 ` [Buildroot] [PATCH 1/3] configs/pine64: bump U-Boot version to 2024.07 Mattia Narducci
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=20240903215308.27bb1d2c@windsurf \
--to=buildroot@buildroot.org \
--cc=jagan@amarulasolutions.com \
--cc=mattianarducci1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox