[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0599fc9c-0057-7aa5-3332-40922753ad97@linaro.org>
Date: Sat, 24 Jun 2023 09:30:13 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: "Lee, Kah Jing" <kah.jing.lee@...el.com>,
Dinh Nguyen <dinguyen@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.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?
Best regards,
Krzysztof
Powered by blists - more mailing lists