3 ms·

Dealing with EFI issues like this right now! It's made worse because we run Windows 10 IoT Enterprise on the devices and much of the work I did on our 64-bit OS

Dealing with EFI issues like this right now! It's made worse because we run Windows 10 IoT Enterprise on the devices and much of the work I did on our 64-bit OS image is mostly invalidated because our next tablet has the exact same processor but only 32-bit EFI.... Oh man, it can really screw with your logistics when you rely on consumer tablets. There's one reason to pay a premium for 'industrial' devices. I will say this additionally though - the messaging around the Intel Atom line, IMHO has been absolutely terrible. If only our software could run on ARM. I was convinced at one stage they were discontinuing the whole thing and then suddenly they didn't? I don't even know anymore. They have a roadmap so I guess that's something. TL;DR: Think very carefully before basing a product on consumer-grade hardware, especially with consumer-grade tablets. To the parent commenter, you're probably lucky you DIDN'T push through it :)

mkl 7y ago
What is it about your software that it can't run on ARM?
- Fr0styMatt88 7y ago
  It's a .NET application that still potentially relies on some third-party x86 binary drivers/components that are only on Windows. Ideally in the future the whole codebase could be ported over to .NET Core, with the remaining native components being stripped out (we've somewhat worked towards this). Really though, it's that we don't have the resources to dedicate to any porting or compatibility effort (I've toyed with the idea of QEMU on ARM) to do it, so unfortunately it's one of those things that gets very slowly pieced together in the background here and there. Too big a project to convince the higher-ups that it's worth the tradeoff of prioritizing it over new features and new customers.