From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2E6AAC54EE9 for ; Mon, 19 Sep 2022 11:12:49 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 985B584C16; Mon, 19 Sep 2022 13:12:47 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=thorsis.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=thorsis.com header.i=@thorsis.com header.b="hne7HJtI"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 7E97C84C19; Mon, 19 Sep 2022 13:12:45 +0200 (CEST) Received: from mail.thorsis.com (mail.thorsis.com [92.198.35.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 3C381843F0 for ; Mon, 19 Sep 2022 13:12:43 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=thorsis.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=ada@thorsis.com Date: Mon, 19 Sep 2022 13:12:41 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thorsis.com; s=default; t=1663585962; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1RhbpwH2CJnL8dVyKRTCnQw8csas0GdIFqHfy/RCr2o=; b=hne7HJtIXnUav2GxJnq1rU4Aeaj4Bvb+twxKTratUiLsSXmAUZKzWNi48KcX5HhF0qiopC elYtrNmBgKvUnRqwQKyvfSvgpYs4UxDm3Nufb8ftF5mkJnOqkGnxgFdbHOv4roxEWjHXOM XcBMQSj4QZ/KEN+ZDrk9p6e2lpr7lrhO9ZoUUQFBqDu3SVUKGAmhfHS1GZo+qexhkoxFeT sXtb9ut91lhqbHt2SSnXLV/lMsXUo6fLI+/eCEGdr8bZ3Pu1RmExghvJjqa4dVTNq9ejDI SsY+0JQD3FJY+VzGtiuKK7J9Th6bxFqTvdIV6gVjTMLXAwR52cTCwvwslBNz1A== From: Alexander Dahl To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: u-boot@lists.denx.de Subject: Re: [PATCH 0/9] Nokia RX-51: Small cleanups and UBI boot test case Message-ID: Mail-Followup-To: Pali =?iso-8859-1?Q?Roh=E1r?= , u-boot@lists.denx.de References: <20220904012906.17718-1-pali@kernel.org> Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220904012906.17718-1-pali@kernel.org> X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean Hello Pali, Am Sun, Sep 04, 2022 at 03:28:57AM +0200 schrieb Pali Rohár: > Do various small fixup/cleanups and extend test script to boot kernel > image from UBI volume. This test verifies that U-Boot UBI implementation > is working and U-Boot can read volume with bootable kernel code > correctly. And therefore CI prevents UBI breakage. > > Note that U-Boot UBIFS code on ARM is currently somehow broken and > trying to mount UBIFS from UBI volume fails :-( I have already tried to > debug this issue but I have no idea why it is failing. Function > check_lpt_crc in unpack_ltab is failing. Volume is for sure correct and > valid because Linux kernel can successfully mount it. And to make it > more suspicious, U-Boot UBIFS is working fine on big endian powerpc > platform. So UBIFS issue is probably endian or arch specific. > (This is UBIFS related, not UBI related.) I had some trouble with UBIFS volumes created by Linux not mountable by U-Boot myself recently. Problem was Linux gained zstd compression support for UBIFS with version 5.3 and that was made default with kernel 5.13. U-Boot does not support zstd compression at least up to version 2022.04 (did not try later ones), and simply refuses to mount those volumes. The error message however was different than yours, but maybe you get an idea what might be wrong. I would certainly check with what features the UBIFS is created and if U-Boot supports that. HTH & Greets Alex > > Pali Rohár (9): > Nokia RX-51: Remove label copy_kernel_start from lowlevel_init.S > Nokia RX-51: Do not clear unknown memory in lowlevel_init.S > Nokia RX-51: Set default SYS_LOAD_ADDR to 0x80008000 > Nokia RX-51: Change UBIFS volume size to 1870 LEBs in test script > Nokia RX-51: Call bootm in test script only when image is valid > Nokia RX-51: Fix documentation how to enable UBI support > Nokia RX-51: Do not set useless ARCH= in test script > Nokia RX-51: Add comment describing kernel image type into test script > Nokia RX-51: Add booting from UBI into test script > > board/nokia/rx51/lowlevel_init.S | 7 +-- > configs/nokia_rx51_defconfig | 2 +- > doc/board/nokia/rx51.rst | 3 +- > test/nokia_rx51_test.sh | 97 +++++++++++++++++++++++++------- > 4 files changed, 82 insertions(+), 27 deletions(-) > > -- > 2.20.1 >