Hi, Arnd, On Sat, May 14, 2022 at 3:33 AM Arnd Bergmann <arnd@xxxxxxxx> wrote: > > On Fri, May 6, 2022 at 3:20 PM Huacai Chen <chenhuacai@xxxxxxxxx> wrote: > > On Fri, May 6, 2022 at 7:41 PM Arnd Bergmann <arnd@xxxxxxxx> wrote: > > > > > > Agreed. I think there can be limited compatibility support for old > > > firmware though, at least to help with the migration: As long as > > > the interface between grub and linux has a proper definition following > > > the normal UEFI standard, there can be both a modern grub > > > that is booted using the same protocol and a backwards-compatible > > > grub that can be booted from existing firmware and that is able > > > to boot the kernel. > > > > > > The compatibility version of grub can be retired after the firmware > > > itself is able to speak the normal boot protocol. > > After an internal discussion, we decide to use the generic stub, and > > we have a draft version of generic stub now[1]. I hope V10 can solve > > all problems. :) > > [1] https://github.com/loongson/linux/tree/loongarch-next-generic-stub > > Can you post v19 to the list? As we have resolved the question on clone() > now (I hope), and you have a prototype for the boot protocol, it sounds > like this can make it into v5.19 after all, but we need to be sure that the > remaining points that Xuerui Wang and Ard Biesheuvel raised are > all addressed, and there is not much time before the merge window. > > I have built a gcc-12.1 based toochain at > https://mirrors.edge.kernel.org/pub/tools/crosstool/ that now includes > loongarch64 suport, please point to that in the cover letter for v10 > in case someone wants to start test building. > > I will be travelling next week, and won't be able to pull your tree > into the asm-generic tree during that time, as I had originally planned. > OK, thanks, I will send a new version today. Huacai > However, you can ask Stephen Rothwell (added to Cc) to add your > git tree to linux-next once you think that you have addressed all of the > remaining review comments, and posted the same version to the > list. This will allow others to more easily test your tree in combination > with the other work that has been queued for the 5.19 release. > > If there are no new show-stoppers, I can help you coordinate > the pull request during the merge window. > > Arnd
