I have access to a Surface RT, and it doesn't affect other WoA devices with the same SoC. ConOut is also unusable on the Surface RT.
-----Message d'origine----- De : Grub-devel [mailto:grub-devel-bounces+mmediouni=gmx...@gnu.org] De la part de my123 (@never_released) Envoyé : mardi 23 août 2016 12:24 À : 'The development of GNU GRUB' <grub-devel@gnu.org> Objet : RE: Windows on ARM machines : UEFI bugs It returns EFI_INVALID_PARAMETER and refuses to work here. (I didn't try to reverse engineer how Windows does it, yet) -----Mesej Asli----- Daripada: Grub-devel [mailto:grub-devel-bounces+mmediouni=gmx...@gnu.org] Bagi Pihak Andrei Borzenkov Hantar: mardi 23 août 2016 12:09 Kepada: The development of GNU GRUB <grub-devel@gnu.org> Subjek: Re: Windows on ARM machines : UEFI bugs On Tue, Aug 23, 2016 at 12:39 PM, my123 (@never_released) <mmedio...@gmx.fr> wrote: > Note that on the Surface RT, the first GOP handle is unusable, th > search for handles has to start at handle 1. This bug doesn’t affect > other WoA devices. > Well, someone who has access to such devices needs to find out how to detect this condition. > > > On WoA(Windows on ARM) machines, ExitBootServices doesn’t work, > especially on nVidia devices. What action should be taken? > Not sure I understand what you say. Could you elaborate on what you are trying to do and what does not work? For booting Windows loader is launched as EFI executable so no ExitBootServices happens. > > > (this is a part of the port of Linux to these machines, after > neutralizing Secure Boot) > _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
