lkml.org 
[lkml]   [2010]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH -v2] x86, pci: Handle fallout pci devices with peer root bus
    On Mon, 14 Jun 2010 10:47:59 -0700
    Yinghai Lu <yinghai.lu@oracle.com> wrote:

    >
    > Graham bisected
    > | commit 3e3da00c01d050307e753fb7b3e84aefc16da0d0
    > | x86/pci: AMD one chain system to use pci read out res
    >
    > cause the SND_HDA_INTEL doesn't work anymore.
    >
    > https://bugzilla.kernel.org/show_bug.cgi?id=16007
    >
    > It turns out that his system with via chipset only have one hypertransport
    > chain, but does have one extra orphan device 80:01.0
    >
    > PCI: Probing PCI hardware (bus 00)
    > PCI: Discovered primary peer bus 80 [IRQ]
    >
    > node 0 link 0: io port [1000, ffffff]
    > TOM: 0000000080000000 aka 2048M
    > node 0 link 0: mmio [e0000000, efffffff]
    > node 0 link 0: mmio [a0000, bffff]
    > node 0 link 0: mmio [80000000, ffffffff]
    > bus: [00, ff] on node 0 link 0
    >
    > Try to make peer root buses to share same mmio/io resources if those peer root
    > buses fall into the same bus range.
    >
    > Also need to update insert_resource to avoid insert same resource two times.

    So 3e3da00c01d050307e753fb7b3e84aefc16da0d0 was supposed to address the
    case where some laptop RAM ranges ended up incorrect. Would using _CRS
    on those machines also address that problem? If so, we should consider
    dropping amd_bus.c like we did with intel_bus.c.

    Yinghai, do you still have people from the RAM bug that could test
    using _CRS data?

    --
    Jesse Barnes, Intel Open Source Technology Center


    \
     
     \ /
      Last update: 2010-06-14 20:19    [W:0.023 / U:95.564 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site