Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <12c68124-9687-d68c-294a-2bfd13338edd@linaro.org>
Date:   Mon, 26 Jun 2023 10:38:30 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Subject: Re: [PATCH 2/2] arch: arm64: configs: Enable UBI and UBIFS
Content-Language: en-US
To:     "Lee, Kah Jing" <kah.jing.lee@intel.com>,
        Dinh Nguyen <dinguyen@kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will@kernel.org>
Cc:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
References: <0d1b3c55-4b11-9e63-e388-191d39d88df1@linaro.org>
 <20230622122114.592791-1-kah.jing.lee@intel.com>
 <25439c1e-c9ef-0dc6-8d91-883d7734d0fd@linaro.org>
 <PH0PR11MB5673A862187810E9986E3C8BCB23A@PH0PR11MB5673.namprd11.prod.outlook.com>
 <125c849f-3746-864f-8b8f-6e0a33aca439@linaro.org>
 <PH0PR11MB567334A09B2D4A1D3DDC09F2CB20A@PH0PR11MB5673.namprd11.prod.outlook.com>
 <0599fc9c-0057-7aa5-3332-40922753ad97@linaro.org>
 <PH0PR11MB56734DB18155588535DC0384CB26A@PH0PR11MB5673.namprd11.prod.outlook.com>
From:   Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
In-Reply-To: <PH0PR11MB56734DB18155588535DC0384CB26A@PH0PR11MB5673.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 26/06/2023 06:16, Lee, Kah Jing wrote:
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> Sent: Saturday, 24 June, 2023 3:30 PM
>> To: Lee, Kah Jing <kah.jing.lee@intel.com>; Dinh Nguyen
>> <dinguyen@kernel.org>; Rob Herring <robh+dt@kernel.org>; Krzysztof
>> Kozlowski <krzysztof.kozlowski+dt@linaro.org>; Conor Dooley
>> <conor+dt@kernel.org>; Catalin Marinas <catalin.marinas@arm.com>; Will
>> Deacon <will@kernel.org>
>> Cc: linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH 2/2] arch: arm64: configs: Enable UBI and UBIFS
>>
>> On 24/06/2023 05:42, Lee, Kah Jing wrote:
>>>>>> So you miss init ramdisk.
>>>>> Currently we are using the bootargs to mount the rootfs from QSPI
>>>>> NOR
>>>> flash:
>>>>> [    0.000000] Kernel command line: earlycon panic=-1 ubi.mtd=1
>>>> root=ubi0:rootfs rootfstype=ubifs rw rootwait
>>>>> Is it possible to mount the ubifs rootfs with the ubifs=m config during
>> boot?
>>>>
>>>> I think yes. rootfs devices are for example modules, so filesystem
>>>> can be as well.
>>> Was going through mtd ubifs page -
>>> http://www.linux-mtd.infradead.org/faq/ubifs.html
>>> Quoted: 'In order to mount UBIFS as the root file system, you have to
>>> compile UBIFS into the kernel (instead of compiling it as a kernel
>>> module) and specify proper kernel boot arguments and make the kernel
>> mount UBIFS on boot.'
>>
>> Why? Module loaded by initramfs would also understand cmdline arguments,
>> right?
> The suggestion is to use initramfs for rootfs -> remount UBIFS as chroot?
> The concern is additional initrd image and steps to store in the
> limited NOR flash (256MB, Boot data + Uboot - ~66MB, UBIFS image - ~88MB, 
> kernel.itb - ~10MB = 164MB).
> With the mounting Rootfs from UBIFS volume, we can skip the initrd step, and
> save some space for the user operations. 
> Let me know if I understands that correctly.

arm64 defconfig creates huge development config for all platforms, so
why would you ever use it in resource-constrained system? It would
barely fit. defconfig modules take 50 MB alone and you don't need most
of them.

I think you misunderstood the purpose of this defconfig and now try to
apply some arguments for different use cases.

Best regards,
Krzysztof