Re: mlx4_core probe error after applying Yinghai's patch

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

 



On Tue, 14 Jan 2014 19:10:55 +0800
Gavin Shan <shangw@xxxxxxxxxxxxxxxxxx> wrote:

> The problem happened only when BAR#0 and BAR#6 were allocated
> from same non-profetchable P2P window. So we guessed the problem
> had relationship with ROM BAR#6 and we read multiple bytes from
> BAR#0+0x8069c:
> 
> BAR#0+0x8069c: 0x00001000
> BAR#0+0x806a0: 0x0
> BAR#0+0x806a4: 0x0
> BAR#0+0x806a8: 0x0
> BAR#0+0x806ac: 0x0
> 
> My question is 0x0 is expected value from (BAR#0 + 0x806a*) ? :-)

Yes, the first time the value is read from dword 0x8069c, it should be
zero.

-Jack
--
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