Efi Support

[JoshuaWierenga]

Several c# features could be added by supporting more low-level EFI functions like time, networking, file systems and graphics. Supporting these features would massively improve support with third-party applications and help make EfiSharp much more useful.

APIs to support:

• [ ] Time support. Requires adding the EFI_TIME struct and the EFI_GET_TIME and EFI_SET_TIME functions within EFI_RUNTIME_SERVICES. See #17.
  • [x] Add efi support. DONE. Should the todos be dealt with?
  • [x] Add c# wrapper, DONE, a lot of DateTime is now supported, including .Now.
• [ ] Networking support. This is a lot of work and requires the EFI_TCP4_PROTOCOL, EFI_MAC_ADDRESS, EFI_DHCP4_PROTOCOL and EFI_IP4_PROTOCOL structs and their functions, if not more.
• [ ] File System Support. Another big project and requires the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL and EFI_FILE_PROTOCOL structs and their functions, if not more.
• [ ] Graphics Support. Requires the EFI_GRAPHICS_OUTPUT_PROTOCOL, EFI_GRAPHICS_OUTPUT_MODE_INFORMATION, and EFI_GRAPHICS_OUTPUT_PROTOCOL_MODE structs and their functions, if not more. Additionally, there is some image/forms stuff in EFI_HII_IMAGE_PROTOCOL, Image Package and Forms Package which looks somewhat useful.
• [x] Random Number Generation. Requires EFI_RNG_PROTOCOL at a minimum and perhaps EFI_RNG_ALGORITHM. See #20.
  • [x] Add efi support. DONE
  • [x] Add c# wrapper. DONE. Added efi specific implementation for all functions except ReadBytes(Span\<byte>).
  • [x] Add Legacy and Xoshiro rng implementations. DONE. Same as above with the additional exception that the seedless constructor in Random.cs always uses Xoshiro.
• [ ] Thread Support
  • [ ] Sleep Support. Requires either CreateEvent, SetTimer and WaitForEvent or Stall, both sets of functions are in EFI_BOOT_SERVICES. Then Thread.Sleep and Thread.InternalSleep to wrap the efi call(s)

Most of these require accessing their protocols via the boot service's protocol handler functions but a few are accessed by EFI_RUNTIME_SERVICES so that appears like a good place to start.

[JoshuaWierenga]

Another useful addition would be debugging, there appears to be two mains ways of doing this. The first would be solely debugging the c# code with its associated runtime which might be possible to do just using visual studio with something like https://github.com/Michael-Kelley/RoseOS/tree/master/WindowsTest. The second option would be doing it directly on efi which should allow everything to be checked using the efi debugger protocol though I have no idea how that works.