[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62e81ce06e69d549b12d1145429730f8b27ad156.camel@hotmail.com>
Date: Sun, 9 Jul 2023 17:35:13 +0000
From: donmor <donmor3000@...mail.com>
To: "chenhuacai@...nel.org" <chenhuacai@...nel.org>
CC: "loongarch@...ts.linux.dev" <loongarch@...ts.linux.dev>,
"kernel@...0n.name" <kernel@...0n.name>,
"yangtiezhu@...ngson.cn" <yangtiezhu@...ngson.cn>,
"zhoubinbin@...ngson.cn" <zhoubinbin@...ngson.cn>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"ardb@...nel.org" <ardb@...nel.org>,
"tangyouling@...ngson.cn" <tangyouling@...ngson.cn>
Subject: Re: [PATCH] loongarch: Make CONFIG_CMDLINE work with
CONFIG_CMDLINE_EXTEND and CONFIG_CMDLINE_BOOTLOADER
在 2023-07-09星期日的 23:30 +0800,Huacai Chen写道:
> How to reproduce? If you use UEFI firmware, this is handled in
> drivers/firmware/efi/libstub/efi-stub.c; if you use non-UEFI firmware,
> this is handled in drivers/of/fdt.c.
In fact it 's not command line retrieved from efi or fdt, but the built-in
command line to be concerned. CONFIG_CMDLINE was never been touched during
boot on loongarch, unless CONFIG_CMDLINE_FORCE is set because there is code
handling this. There should be code handling CONFIG_CMDLINE_FORCE and
CONFIG_CMDLINE_EXTEND as well but is absent by now.
Powered by blists - more mailing lists