Re: failed to access the mem resource space of the pcie device on arm platform

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Bjorn
The x86 lspci is not related to my arm system, just a lspci log referrence.

I only have one 4965agn mini pcie card, not sure that any PCIe cards
can work on my platform or not.
BTW, I don't have the PCIe analyzer either.
So it's hard to debug the PCIe RC and ahcive the breakthrough.

Best Regards
Richard Zhu.

On 28 October 2011 00:03, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
> I have no idea.  I don't know how the x86 lspci is related at all.  Is
> it related to your arm system somehow?
>
> Do any PCIe cards work on the arm system?  Can you use a PCIe analyzer
> to see if any MMIO transactions appear on the link?
>
> On Thu, Oct 27, 2011 at 1:04 AM, Richard Zhu <richard.zhu@xxxxxxxxxx> wrote:
>> Hi Bjorn:
>> About the complete lspci on x86 and the dmesg on arm platform, pls
>> refer to the attached file.
>>
>> Thanks.
>>
>> Best Regard.
>>
>> On 26 October 2011 22:08, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
>>> On Wed, Oct 26, 2011 at 4:08 AM, Richard Zhu <richard.zhu@xxxxxxxxxx> wrote:
>>>> Hi Bjorn:
>>>> Thanks for your comments firstly.
>>>> The platform only has one PCIe RC mode host, connected one INTEL
>>>> 4965AGN wifi card.
>>>> Doesn't have PCIe bridge device.
>>>>
>>>> The following log is generated on one X86 machine. It seems that the
>>>> 00:00:0 is assigned to the PCI bridge device, is it?
>>>> "00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 13)"
>>>
>>> If you attached a dmesg log, I didn't get it.  How about the complete
>>> "lspci" output, too?
>>>
>>>> About the device address, do you means that the RC mode PCIe host
>>>> should be scanned,
>>>> and assigned the address too?
>>>
>>> I just mean that normal devices (NICs, storage HBAs, USB, VGA, etc.,)
>>> usually are not at bus 0, device 0, function 0.  The fact that your
>>> wifi NIC is apparently is at bus 0, device 0, function 0, is unusual,
>>> so I would investigate that.  Maybe there's something wrong with your
>>> platform's PCI device enumeration.
>>>
>>>>> A complete dmesg log is always a good start.
>>>>>
>>>>> I don't see anything obviously wrong.  The device address (bus 0,
>>>>> device 0, function 0) is unusual, so I'd double-check that.  At least
>>>>> on x86, 00:00.0 is usually something in the north bridge, not a normal
>>>>> device.
>>>>>
>>>>> Bjorn
>>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux