Hi Bjorn,
On 5/30/2018 10:43 AM, Ray Jui wrote:
Hi Bjorn,
On 5/30/2018 10:27 AM, Bjorn Helgaas wrote:
On Thu, May 17, 2018 at 10:21:31AM -0700, Ray Jui wrote:
On certain versions of Broadcom PAXC based root complexes, certain
regions of the configuration space are corrupted. As a result, it
p
Hi Bjorn,
On 5/30/2018 10:27 AM, Bjorn Helgaas wrote:
On Thu, May 17, 2018 at 10:21:31AM -0700, Ray Jui wrote:
On certain versions of Broadcom PAXC based root complexes, certain
regions of the configuration space are corrupted. As a result, it
prevents the Linux PCIe stack from traversing the l
On Thu, May 17, 2018 at 10:21:31AM -0700, Ray Jui wrote:
> On certain versions of Broadcom PAXC based root complexes, certain
> regions of the configuration space are corrupted. As a result, it
> prevents the Linux PCIe stack from traversing the linked list of the
> capability registers completely
On 2018-05-17 22:51, Ray Jui wrote:
On certain versions of Broadcom PAXC based root complexes, certain
regions of the configuration space are corrupted. As a result, it
prevents the Linux PCIe stack from traversing the linked list of the
capability registers completely and therefore the root comp
On certain versions of Broadcom PAXC based root complexes, certain
regions of the configuration space are corrupted. As a result, it
prevents the Linux PCIe stack from traversing the linked list of the
capability registers completely and therefore the root complex is
not advertised as "PCIe capable
5 matches
Mail list logo
