From: "Longhorn" <mmediouni@gmx.fr>
To: "'The development of GNU GRUB'" <grub-devel@gnu.org>
Subject: RE: Windows on ARM machines : UEFI bugs
Date: Tue, 23 Aug 2016 12:28:30 +0200 [thread overview]
Message-ID: <004701d1fd29$18d2a700$4a77f500$@gmx.fr> (raw)
In-Reply-To: <006d01d1fd28$88754140$995fc3c0$@gmx.fr>
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.fr@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.fr@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) <mmediouni@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
next prev parent reply other threads:[~2016-08-23 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 9:32 Windows on ARM machines : UEFI bugs my123 (@never_released)
2016-08-23 9:39 ` my123 (@never_released)
2016-08-23 10:09 ` Andrei Borzenkov
2016-08-23 10:24 ` my123 (@never_released)
2016-08-23 10:28 ` Longhorn [this message]
2016-08-23 11:10 ` Andrei Borzenkov
2016-08-23 11:18 ` Longhorn
2016-08-23 11:20 ` Andrei Borzenkov
2016-08-23 11:21 ` Longhorn
2016-08-23 11:43 ` Andrei Borzenkov
2016-08-23 11:45 ` Longhorn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004701d1fd29$18d2a700$4a77f500$@gmx.fr' \
--to=mmediouni@gmx.fr \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).