windows-drivers
windows-drivers copied to clipboard
raspberrypi
Some info about this repository?
Are there any plans to fully support Windows 10 (IoT?) on the Raspberry Pi 4?
Recently got second monitor support working, a little bit temperamental at this stage but it's great to see it working at least https://github.com/TheMindVirus/pi4bdd
Are there any plans to fully support Windows 10 (IoT?) on the Raspberry Pi 4?
AFAIK Windows 10 IoT (non Enterprise) exists only in 32-bit ARM flavor, so supporting it means we'll need 32-bit ARM UEFI firmware and drivers accordingly.
Are there any plans to fully support Windows 10 (IoT?) on the Raspberry Pi 4?
AFAIK Windows 10 IoT (non Enterprise) exists only in 32-bit ARM flavor, so supporting it means we'll need 32-bit ARM UEFI firmware and drivers accordingly.
Looks like Windows 10 IoT Core ARM64 packages are available in the 1809 January Refresh link so in theory those could be used to bring up Windows IoT Core on the ARM64 RPi4 baseline.
Disclaimer: Opinions expressed here are solely my own and do not express the views or opinions of my employer.
The issue with IoT Core is that the last version is RS5 (17763), but the GENET (integrated ethernet controller of Pi4) driver targets 19041. You'll have to use USB LAN adapters if you want internet connectivity.
Also IoT Core ARM64 does not come with any UI built-in (and shows a black screen if you don't install/run any app, the default UI App you saw on IoT Core normally is open source though), and does not have any form of WOW64 whatsoever, only ARM64 apps (UWP or Win32 Console) will run.
The issue with IoT Core is that the last version is RS5 (17763), but the GENET (integrated ethernet controller of Pi4) driver targets 19041.
Is it possible to downgrade the target, if it's not too much maintenance? I think it would be nice to support it despite known limitations.
Is it possible to downgrade the target, if it's not too much maintenance? I think it would be nice to support it despite known limitations.
The driver is based on NetAdapterCx framework, which is only available (in preview) in 19041+, that is also why we have three version of the driver for different builds of Windows, the framework API is not stable yet... Not sure why @alotipac decided this route (easier development?). "Retargetting" it to lower version will mean a complete rewrite.