linux-kernel - Re: [PATCH V11 09/22] LoongArch: Add boot and setup routines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <14f922495a09898017e4db3baed5b434acadac12.camel@xry111.site>
Date:   Tue, 24 May 2022 16:27:13 +0800
From:   Xi Ruoyao <xry111@...111.site>
To:     Huacai Chen <chenhuacai@...ngson.cn>,
        Arnd Bergmann <arnd@...db.de>,
        Andy Lutomirski <luto@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        David Airlie <airlied@...ux.ie>,
        Jonathan Corbet <corbet@....net>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     linux-arch@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, Xuefeng Li <lixuefeng@...ngson.cn>,
        Yanteng Si <siyanteng@...ngson.cn>,
        Huacai Chen <chenhuacai@...il.com>,
        Guo Ren <guoren@...nel.org>, Xuerui Wang <kernel@...0n.name>,
        Jiaxun Yang <jiaxun.yang@...goat.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        linux-efi@...r.kernel.org, Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH V11 09/22] LoongArch: Add boot and setup routines

On Wed, 2022-05-18 at 17:26 +0800, Huacai Chen wrote:
> Currently an existing interface between the kernel and the bootloader
> is  implemented. Kernel gets 2 values from the bootloader, passed in
> registers a0 and a1; a0 is an "EFI boot flag" distinguishing UEFI and
> non-UEFI firmware, while a1 is a pointer to an FDT with systable,
> memmap, cmdline and initrd information.

If I understand this correctly, we can:

- set a0 to 0
- set a1 a pointer (virtual address or physical address?) to the FDT
with these information

in the bootloader before invoking the kernel, then it will be possible
to boot this kernel w/o firmware update?

I'd prefer to receive a firmware update anyway, but we need an
alternative if some vendor just say "no way, our customized distro works
fine and you should use it".  (I'm not accusing LoongArch: such annoying
behavior is common among vendors of all architectures, and even worse
with x86 because they often say "just use Windoge".)
-- 
Xi Ruoyao <xry111@...111.site>
School of Aerospace Science and Technology, Xidian University