-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preliminary ARM64 IoT Core BSP #43
base: master
Are you sure you want to change the base?
Conversation
91a2dc5
to
81de9f7
Compare
USB Root Hub INF on builds (RS5 or earlier) with broken XHCI driver. On these builds, the Hardware ID of the root hub would become B\ROOT_HUB30# instead of the normal USB\ROOT_HUB30 and the stock INF will fail to work.
The new RPi3.ARM64 and RPi4.ARM64 BSP will be side by side with the existing RPi ARM32 BSP for RPi2/3. Move RPi to its own directory to avoid conflition. binexport scripts will be updated when the new BSPs are added.
While trying to upstream a revert patch does not make much sense, one can try to make a patch that will allow to switch between MS-specific function and the standard The switch can be then added to the UEFI setup application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
This adds two new BSPs: RPi3.ARM64 and RPi4.ARM64.
Currently they require UEFI firmware from PFTF to be manually added to
bspfiles/RPix.ARM64/Packages/RPi.BootFirmware
before exporting the BSP.Also the proprietary USB and LAN drivers for Pi3 are not included, and have to be manually added.
A special INF file, rpirshub3.inf, is added to bring up XHCI on Pi 4 on Windows builds <= RS5.
Check out https://github.com/driver1998/windows-drivers/blob/arm64-iot/IOTARM64.md for more details.
Current Status: