All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roberto Medina <robertoxmed@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A
Date: Mon, 4 Nov 2024 23:14:24 +0100	[thread overview]
Message-ID: <20241104231424.4c39ed7d@windsurf> (raw)
In-Reply-To: <20241025093248.2015508-2-robertoxmed@gmail.com>

Hello Roberto,

On Fri, 25 Oct 2024 10:32:48 +0100
Roberto Medina <robertoxmed@gmail.com> wrote:

> - Bump Linux to 6.6.56 (LTS).
> - Bump U-Boot to 2024.07, so it contains commit ebb0ad4eef0a ("arch: arm:
> mach-rockchip: Kconfig: Enable BOOTSTD_FULL for RK3399 and RK3588").
> - Bump TF-A to 2.11.
> - Enable hash checking: BR2_DOWNLOAD_FORCE_CHECK_HASHES.
> - Add relevant hashes in the patches folder for the board.
> - Use uClibc for toolchain instead of Glibc.

Thanks a lot for the new iteration, but why are you switching to
uclibc? We don't want our defconfigs to select particular toolchain
options: they should use the default provided by Buildroot.

Could you send a v3 without this change to uclibc, or provide an
explanation?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-11-04 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  9:32 [Buildroot] [PATCH v2 0/1] configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A Roberto Medina
2024-10-25  9:32 ` [Buildroot] [PATCH v2 1/1] " Roberto Medina
2024-11-04 22:12   ` Julien Olivain
2024-11-04 22:14   ` Thomas Petazzoni via buildroot [this message]
2024-11-17 22:05     ` Roberto Medina

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=20241104231424.4c39ed7d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=robertoxmed@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 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.