From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 11 Aug 2025 15:36:25 +0200 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ulShN-009Loh-2m for lore@lore.pengutronix.de; Mon, 11 Aug 2025 15:36:25 +0200 Received: from bombadil.infradead.org ([2607:7c80:54:3::133]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ulShN-00084i-8V for lore@pengutronix.de; Mon, 11 Aug 2025 15:36:25 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=XRFifV2AMoLT5B02U+UU+qz49w7q8uRrHxIgj73J5EQ=; b=itC23H7HUJlOcwlxQRqvcrdbiz ec0uI+MOB8MxkA+KLVRdFkanr1Oi9ZjMkFWuIP0bv2wU51RbxdljFsyRGmbs7v+BYcONhJeoszja5 DAjz6UF2HxuOeW89NIgWYUAdNJb5CpMaukPVhdbaNCTJPYSnabN9LHkPbEhsjzcSQ3DFCJPIaP61F U4NnXbEuytbpOOUc1o36VRkvZ/UVMwfHlyvAPk1BnDJFwjVfBDWe1+5jDXyIDRKLOGy2mJ/OX3M5z p1VMkg6LnNQIeV4zY+qHojOlCJZbLu+9RA+VJgnizalpnAppTmJURjWl8NiB5sLMgVKyN2xm7NsBw J4+3Dnlw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1ulSgw-00000007qKz-0M06; Mon, 11 Aug 2025 13:35:58 +0000 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1ulSfD-00000007puO-33kJ for barebox@lists.infradead.org; Mon, 11 Aug 2025 13:34:13 +0000 Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77] helo=[127.0.0.1]) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1ulSfA-0007e5-Tc; Mon, 11 Aug 2025 15:34:08 +0200 Message-ID: <44262515-aff5-4162-84e0-b1a1a44208b8@pengutronix.de> Date: Mon, 11 Aug 2025 15:34:08 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Sascha Hauer , Ahmad Fatoum Cc: barebox@lists.infradead.org, chalianis1@gmail.com References: <20250730055743.922932-1-a.fatoum@barebox.org> <20250730055743.922932-2-a.fatoum@barebox.org> Content-Language: en-US, de-DE, de-BE From: Ahmad Fatoum In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250811_063411_773519_0D257FD7 X-CRM114-Status: GOOD ( 22.42 ) X-BeenThere: barebox@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "barebox" X-SA-Exim-Connect-IP: 2607:7c80:54:3::133 X-SA-Exim-Mail-From: barebox-bounces+lore=pengutronix.de@lists.infradead.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.whiteo.stw.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-5.2 required=4.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.2 Subject: Re: [PATCH 2/4] ARM64: configs: multi_v8: disable layerscape temporarily X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on metis.whiteo.stw.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 >> --- >> 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 |