On 29 May 2017 at 16:14, Scott Telford <[email protected]> wrote: >> From: Ard Biesheuvel [mailto:[email protected]] >> Sent: 26 May 2017 18:38 >> To: Leif Lindholm <[email protected]> >> Cc: Scott Telford <[email protected]>; [email protected] <edk2- >> [email protected]>; Tian, Feng <[email protected]>; Zeng, Star >> <[email protected]> >> Subject: Re: [edk2] [PATCH] Copy bus scanning workaround from ARM Juno >> PCIe driver. > >> I'd still like to understand why this issue does not occur under >> Linux, or if it does occur, if we need an ECAM quirk for Juno to work >> around it. >> >> Could you give an example of which hardware combination triggers this >> issue? > > I don't have access to a Juno board here, so can't reproduce the original > problem. It would certainly be interesting to know if the current Juno > platform code using the generic PCIe driver suffers from the same problem or > not. > > The platform I've been working with only exists within a Cadence emulation > environment. I've seen the problem when testing an ASMedia ASM1182e bridge > and an Intel I210 Ethernet card so it's probably not specific to certain PCIe > bridges/devices. > > The original Juno PCIe driver (including the workaround) was committed by > Olivier Martin at ARM, but I'm not sure if he's still there? >
He used to maintain the ARM bits in Tianocore/EDK2 but he left ARM two years ago. > I'm working on moving the workaround into the PciExpressLib layer. > Yes, that is best for now. _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
