-
Notifications
You must be signed in to change notification settings - Fork 39
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
Integrating iPXE driver binary into https://github.com/tianocore/edk2-non-osi for Pi? #3
Comments
Also we'd love to see you hang out in the new Arm Developer-Ecosystem Discord server (invite - https://discordapp.com/invite/fqRhc8y). The Pi 3/4 UEFI devs hang out in #rpi4-uefi-dev. See https://rpi4-uefi.dev/ - it's the same upstream Pi 3 UEFI code, but we're mostly focusing on Pi 4 support now (although unifying code where possible means there's quite a bit of Pi 3 hackery happening, too) |
@andreiw Thanks for the invitation. I've been meaning to reply to this for months, but am only now getting around to dealing with the insane e-mail backlog I allowed to build up. I'm happy for you to push known-working iPXE binaries into the edk-non-osi tree if that makes life easier for anyone! I've joined the Discord server: hopefully you can find me there as |
Hi Michael,
It's been a while since we last chatted (GSoC 2012? 2011?).
First of all big thanks for your fixes/cleanups to the Tiano DWC2 driver. And thanks for pipxe.
How do you feel about checking in a known iPXE build as part of the edk2 tree for Pi 3/4? Today we check-in the Trusted Firmware prebuilts into https://github.com/tianocore/edk2-non-osi (TF-A is OSS, but it's not Tiano code, and as a binary blob that's where it goes).
Distributing iPXE would mean supporting a wider set of USB-based NICs on Pi 3 and Pi 4 (including the onboard NIC on Pi 3). This would remove the need to maintain a separate pipxe repo here.
A
The text was updated successfully, but these errors were encountered: