Hi Ruoyao, I got a message from Huacai that you want to get the firmware that can boot this kernel, so what kind of machine do you have? Can you provide information on SMBIOS type0, type1 and type2 of the machine at hand? I think it would be better if you could provid the image of machine and motherboard. Referring to Huacai, we are going create a webpage on the Github that can provide the firmware which can boot the new interface kernels, we will provide as many kinds of machine firmware as possible, including qemu firmware. I beleve it will see you soon. :) Thanks, Chao > -----原始邮件----- > 发件人: "Huacai Chen" <chenhuacai@xxxxxxxxx> > 发送时间: 2022-05-24 18:59:50 (星期二) > 收件人: "Xi Ruoyao" <xry111@xxxxxxxxxxx>, lichao@xxxxxxxxxxx > 抄送: "Huacai Chen" <chenhuacai@xxxxxxxxxxx>, "Arnd Bergmann" <arnd@xxxxxxxx>, "Andy Lutomirski" <luto@xxxxxxxxxx>, "Thomas Gleixner" <tglx@xxxxxxxxxxxxx>, "Peter Zijlstra" <peterz@xxxxxxxxxxxxx>, "Andrew Morton" <akpm@xxxxxxxxxxxxxxxxxxxx>, "David Airlie" <airlied@xxxxxxxx>, "Jonathan Corbet" <corbet@xxxxxxx>, "Linus Torvalds" <torvalds@xxxxxxxxxxxxxxxxxxxx>, linux-arch <linux-arch@xxxxxxxxxxxxxxx>, "open list:DOCUMENTATION" <linux-doc@xxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, "Xuefeng Li" <lixuefeng@xxxxxxxxxxx>, "Yanteng Si" <siyanteng@xxxxxxxxxxx>, "Guo Ren" <guoren@xxxxxxxxxx>, "Xuerui Wang" <kernel@xxxxxxxxxx>, "Jiaxun Yang" <jiaxun.yang@xxxxxxxxxxx>, "Stephen Rothwell" <sfr@xxxxxxxxxxxxxxxx>, linux-efi <linux-efi@xxxxxxxxxxxxxxx>, "Ard Biesheuvel" <ardb@xxxxxxxxxx> > 主题: Re: [PATCH V11 09/22] LoongArch: Add boot and setup routines > > Hi, Ruoyao, > > On Tue, May 24, 2022 at 4:27 PM Xi Ruoyao <xry111@xxxxxxxxxxx> wrote: > > > > 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? > Unfortunately, there is no released firmware for you since we recently > changed the interface again and again. :( > You can contact with Li Chao (lichao@xxxxxxxxxxx), I think he can > provide help as much as possible (at least provide temporary firmwares > for developers). > We will also provide qemu-system and virtual machine's firmware as > soon as possible. > > Huacai > > > > > 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@xxxxxxxxxxx> > > School of Aerospace Science and Technology, Xidian University </xry111@xxxxxxxxxxx></xry111@xxxxxxxxxxx></ardb@xxxxxxxxxx></linux-efi@xxxxxxxxxxxxxxx></sfr@xxxxxxxxxxxxxxxx></jiaxun.yang@xxxxxxxxxxx></kernel@xxxxxxxxxx></guoren@xxxxxxxxxx></siyanteng@xxxxxxxxxxx></lixuefeng@xxxxxxxxxxx></linux-kernel@xxxxxxxxxxxxxxx></linux-doc@xxxxxxxxxxxxxxx></linux-arch@xxxxxxxxxxxxxxx></torvalds@xxxxxxxxxxxxxxxxxxxx></corbet@xxxxxxx></airlied@xxxxxxxx></akpm@xxxxxxxxxxxxxxxxxxxx></peterz@xxxxxxxxxxxxx></tglx@xxxxxxxxxxxxx></luto@xxxxxxxxxx></arnd@xxxxxxxx></chenhuacai@xxxxxxxxxxx></xry111@xxxxxxxxxxx></chenhuacai@xxxxxxxxx> 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。 This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.
