On 5/27/2015 12:54 PM, Lorenzo Pieralisi wrote:
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> >index 062fee6..335d9f2 100644
> >--- a/drivers/pci/probe.c
> >+++ b/drivers/pci/probe.c
> >@@ -453,7 +453,11 @@ void pci_read_bridge_bases(struct pci_bus *child)
> > struct resource *re
On Wed, May 27, 2015 at 05:42:52PM +0100, Suravee Suthikulanit wrote:
> Hi Lorenzo,
>
> Sorry for late reply.
>
> On 5/21/2015 8:14 AM, Lorenzo Pieralisi wrote:
> > When a PCI bus is scanned, upon PCI bridge detection the kernel
> > has to read the bridge registers to set-up its resources so that
Hi Lorenzo,
Sorry for late reply.
On 5/21/2015 8:14 AM, Lorenzo Pieralisi wrote:
When a PCI bus is scanned, upon PCI bridge detection the kernel
has to read the bridge registers to set-up its resources so that
the PCI resource hierarchy can be validated properly.
Most if not all architectures
On Tue, May 26, 2015 at 01:57:59PM +0100, Will Deacon wrote:
> Hi Lorenzo,
>
> On Thu, May 21, 2015 at 02:14:25PM +0100, Lorenzo Pieralisi wrote:
> > When a PCI bus is scanned, upon PCI bridge detection the kernel
> > has to read the bridge registers to set-up its resources so that
> > the PCI res
Hi Lorenzo,
On Thu, May 21, 2015 at 02:14:25PM +0100, Lorenzo Pieralisi wrote:
> When a PCI bus is scanned, upon PCI bridge detection the kernel
> has to read the bridge registers to set-up its resources so that
> the PCI resource hierarchy can be validated properly.
>
> Most if not all architect
When a PCI bus is scanned, upon PCI bridge detection the kernel
has to read the bridge registers to set-up its resources so that
the PCI resource hierarchy can be validated properly.
Most if not all architectures read PCI bridge registers in the
pcibios_fixup_bus hook, that is called by the PCI ge
6 matches
Mail list logo
