From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Ahmad Fatoum <a.fatoum@barebox.org>
Cc: barebox@lists.infradead.org, chalianis1@gmail.com
Subject: Re: [PATCH 2/4] ARM64: configs: multi_v8: disable layerscape temporarily
Date: Mon, 11 Aug 2025 15:34:08 +0200 [thread overview]
Message-ID: <44262515-aff5-4162-84e0-b1a1a44208b8@pengutronix.de> (raw)
In-Reply-To: <aJGZ7jn-qGjkPxXo@pengutronix.de>
Hello Sascha,
On 8/5/25 07:43, Sascha Hauer wrote:
> Hi Ahmad,
>
> On Wed, Jul 30, 2025 at 07:57:41AM +0200, Ahmad Fatoum wrote:
>> With multi_v8, we build everything in a single build and that makes the
>> layerscape PBLs exceed their hard limit of 64K failing the build.
>
> This doesn't happen here. The biggest PBL I get here is the ls1046ardb
> one with 58304 bytes. Are you using some other compiler than me?
>
> The Layerscape PBLs for the other boards are much smaller because they
> don't use a fixed SDRAM controller setup rather than detecting DIMMs via
> SPD. Would it be enough to disable the LS1046ardb board?
I can't reproduce it now, but seem to recall I didn't change anything
intentionally..
We already have a layerscape defconfig for people intent on using the
RDB. Most other people don't care about this board for
multi_v8_defconfig, so it's unfortunate that you can't enable things
without risking build breakage.
I have patches that I need to finish in the coming months that make too
big images a soft error like we do for missing firmware. I would prefer
we add back Layerscape support after these patches are merged.
Thanks,
Ahmad
>
> Sascha
>
>>
>> Until resolved, let's disable it from the defconfig. Users can still use
>> the dedicated layerscape defconfigs.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
>> ---
>> arch/arm/configs/multi_v8_defconfig | 5 -----
>> 1 file changed, 5 deletions(-)
>>
>> diff --git a/arch/arm/configs/multi_v8_defconfig b/arch/arm/configs/multi_v8_defconfig
>> index a487d331d04e..5c295cd58269 100644
>> --- a/arch/arm/configs/multi_v8_defconfig
>> +++ b/arch/arm/configs/multi_v8_defconfig
>> @@ -3,7 +3,6 @@ CONFIG_ARCH_BCM283X=y
>> CONFIG_ARCH_IMX=y
>> CONFIG_ARCH_K3=y
>> CONFIG_ARCH_SUNXI=y
>> -CONFIG_ARCH_LAYERSCAPE=y
>> CONFIG_ARCH_ROCKCHIP=y
>> CONFIG_ARCH_ZYNQMP=y
>> CONFIG_MACH_RPI3=y
>> @@ -28,9 +27,6 @@ CONFIG_MACH_ZII_IMX8MQ_DEV=y
>> CONFIG_MACH_PHYTEC_PHYCORE_IMX93=y
>> CONFIG_MACH_TQMA93XX=y
>> CONFIG_IMX_IIM=y
>> -CONFIG_MACH_LS1028ARDB=y
>> -CONFIG_MACH_LS1046ARDB=y
>> -CONFIG_MACH_TQMLS1046A=y
>> CONFIG_MACH_BEAGLEPLAY=y
>> CONFIG_MACH_RK3568_EVB=y
>> CONFIG_MACH_RK3568_BPI_R2PRO=y
>> @@ -258,7 +254,6 @@ CONFIG_REGULATOR_FIXED=y
>> CONFIG_REGULATOR_ARM_SCMI=y
>> CONFIG_REGULATOR_RK808=y
>> CONFIG_RESET_IMX7=y
>> -CONFIG_PCI_LAYERSCAPE=y
>> CONFIG_PCI_ECAM_GENERIC=y
>> CONFIG_RTC_CLASS=y
>> CONFIG_RTC_DRV_DS1307=y
>> --
>> 2.39.5
>>
>>
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-08-11 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 5:57 [PATCH 1/4] scripts: Makefile.pic: define __NO_FORTIFY without value Ahmad Fatoum
2025-07-30 5:57 ` [PATCH 2/4] ARM64: configs: multi_v8: disable layerscape temporarily Ahmad Fatoum
2025-08-05 5:43 ` Sascha Hauer
2025-08-11 13:34 ` Ahmad Fatoum [this message]
2025-07-30 5:57 ` [PATCH 3/4] ARM: configs: multi: configure CONFIG_CONSOLE_ACTIVATE_ALL_FALLBACK Ahmad Fatoum
2025-07-30 5:57 ` [PATCH 4/4] ARM64: configs: add multi_v8_efi_defconfig Ahmad Fatoum
2025-08-11 13:34 ` [PATCH 1/4] scripts: Makefile.pic: define __NO_FORTIFY without value Sascha Hauer
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=44262515-aff5-4162-84e0-b1a1a44208b8@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.org \
--cc=chalianis1@gmail.com \
--cc=s.hauer@pengutronix.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