On 09/24/15 23:17, Shubha Ramani wrote: > I haven't tried that. I don't know how to get the debug output of the PCI Bus > driver. Can you elaborate Lazlo ?
Please -- my first name is Laszlo, not Lazlo. I realize there might be no difference in pronunciation for someone who doesn't speak Hungarian, but at least try to copy&paste it. :) Anyway I shouldn't obsess about this, you are not the first and not the last person. I've seen practically all possible permutations and variations of the substring "szl" when being addressed in writing. Anyway. For seeing the debug output of the PCI bus driver, you should set the gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel log mask PCD in your DSC file to something nicely verbose. The meaning of the individual bits is defined in MdePkg/Include/Library/DebugLib.h. My personal preference is 0x8040004F. Then you should ensure that the DebugLib library class is resolved to a sensible library instance on your platform. This can be done in the DSC file too, at various levels of generality. You can look at OvmfPkg/*.dsc for some examples. For your use case, I can find four candidates in the edk2 tree: MdePkg/Library/BaseDebugLibSerialPort/BaseDebugLibSerialPort.inf MdePkg/Library/UefiDebugLibConOut/UefiDebugLibConOut.inf MdePkg/Library/UefiDebugLibDebugPortProtocol/UefiDebugLibDebugPortProtocol.inf MdePkg/Library/UefiDebugLibStdErr/UefiDebugLibStdErr.inf Each directs the DEBUG messages to a different place (or underlying protocol), and is usable in different module types. Please consult the INF files, and pick one that matches your development platform best. When the right log mask is set, and you build with -b DEBUG, and the right DebugLib instance is linked into the PCI Bus driver, you will see the debug messages about the PCI enumeration. Thanks Laszlo > > Sent from Shubha Ramani's iPhone 6 Plus > >> On Sep 24, 2015, at 2:07 PM, Laszlo Ersek <[email protected]> wrote: >> >>> On 09/24/15 22:52, Shubha Ramani wrote: >>> >>> Please see the code below which follows 1 b) in Lazlo's detailed >>> email suggestion of a few days ago. The code is not seeing Bus 1. >>> It's only seeing Bus 0.Does this have something to do with passing >>> gEfiPciIoProtocolGuid into LocateHandleBuffer ?I noticed that there >>> is also gEfiLegacyBiosGuid and gEfiSimpleTextInProtocolGuid(in >>> perusing "LegacyPci.c"). The PCI device in question is a proprietary >>> Intel chip. I checked with the design team and these registersare >>> definitely visible to UEFI drivers. So I'm wondering why the code is >>> not seeing Bus 1. Any suggestions ? >> >> Can you see the relevant device (BFD) in the debug output of the PCI Bus >> driver? >> >> PciBus: Discovered PCI @ [..|..|..] >> >> Laszlo >> > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
