On 11/29/2018 11:01 AM, Jon Masters wrote:
On 11/28/18 9:31 AM, Alexander Graf wrote:

I got a new toy this week: An HP Envy X2 system. This is one of those shiny
new Qualcomm Snapdragon based Windows tablet/notebook hybrid things.
Cool! I've got one too, and hadn't poked since we looked a while back,
so it'll be great to have a motivation to look at this again soon!

While running Windows on those is actually not a terribly bad experience now
that WSL is out, I would like to see Linux run on those as well in the future.

Unfortunately as far as I'm aware so far nobody was able to run self built
binaries on the built-in UEFI version.

Turns out, it's a problem with aligning the start of the header to 4k. Once
we do that, binaries can be loaded just fine and run.

So to maintain compatibility with that device, this patch set just bumps the
header alignment to 4K always on arm64-efi. This shouldn't hurt too much for
not affected targets and allows us to have a single grub binary that can then
chain load Linux properly.
This is awesome work. Obvious when you know it, but glad you did the
hard work to figure that out. I'm thinking Leif is right, we should try
to get HP to fix their firmware, especially since we know what is
broken. If Leif ends up needing any help prodding HP, we can try to
figure out who to talk to, or ask some other friends for assistance.

If you manage to convince them (and MS to roll it out automatically), that would obviously be the better alternative. They seem to have capsule updates on there, so I assume there are channels in place.

While you're at it, could you also poke them to up their FADT to 5.1? The fact they're on 5.0 is the main reason Linux doesn't boot.

I owe you another tea ;)

Oh, memories :). I'll tell you what happened after that tea next time we bump into each other ;). Maybe for that I'll need something stronger though.


Cheers,

Alex


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to