I think we should understand if this is being driven by some kind of standard? Maybe the Flat Device Tree lib should be part of the MdePkg? Or maybe MdeModulePkg? Thanks, Andrew Fish

Marvin, Sorry I started looking at the code and forgot to give the history. The dlopen() was a trick copied from the Windows port. Basically an EFI image is loaded into EFI memory and it is also loade

You can run the `memmap` command at the EFI Shell to see the layout. Print != printf on some of the format string so be careful about that…. Thanks, Andrew Fish

The requiring *.pdb seems like something that rotted out and could be fixed. This code is very very old. Notice the comment about gdb predates gdb Python support [1]. What happens if you comment out t

The EFI System Partition is defined to be FAT32 by the UEFI Spec for interoperability. It defines the file system drivers required for the firmware and OS. So changing that is not really an option. Yo

Marvin, Good point that the FatPkg was more about license boundary than anything else, so I’m not opposed to a more generic package name. I think having a default PCD option of read only is a good ide

Reviewed-by: Andrew Fish <afish@...>

I think the Terminal driver may have some similar logic to convert UTF-8 terminals to/from the UEFI UCS-2? https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Universal/Console/TerminalDxe/Vtut

Reviewed-by: Andrew Fish <afish@...>

Rebecca, Makes sense to move the instructions over to brew I guess. Thanks, Andrew Fish

These Xcode instructions look good to me in general. Thanks for doing this I usually do things following a non public path. I think to make these instructions work you need to update *_XCODE5_*_MTOC_P

Reviewed-by: Andrew Fish <afish@...>

I don’t think we would need to change PEI. 1s you need to figure out which UsbIo service you would need to code the USB Audio driver against. MdePkg/Include/Protocol/UsbIo.h:485: EFI_USB_IO_ISOCHRONOU

I’ve got a branch on a private repo (BZ3500-gdb @ https://github.com/ajfish/edk2.git) that has gdb and lldb scripts that can attach to QEMU and symbolicate EFI. These scripts also provide other useful

If I `OvmfPkg/builds.sh qemu -usb -device usb-audio -device qemu-xhci` I see 2 USB handle? When you open EXCLUSIVE you are kicking other people off the handles. I’m not sure that is a good idea for yo

Ethin, The UEFI Shell `dh` command UI uses handle numbers from 0 - N as hex digits. You have use these abstract values with the `dh` command. For example: use `dh -v A1` to see the actual handle value

How are you constructing handle[]? Could it have gotten stale? You could print out the value of handle[I] on the failure. The contents of a handle are not defined, but the current implementation is a

Resending without attachments….

It got removed since it is obsolete. I wrote it a long time ago as part of the Embedded Boot Loader (EBL). The EBL was a proof of concept I wrote in something like 2007 to show an EFI system could hav

I’ve been watching the Le Tour replays and playing around with gdb scripts. I was trying to figure out how to do stuff I know how to do in lldb. For lldb I have Pretty Printer and for CHAR16 things li