linux-kernel - PCI device memory bar access issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4862FE1C.8020500@alcatel-lucent.com>
Date:	Thu, 26 Jun 2008 10:25:32 +0800
From:	gshan <gshan@...atel-lucent.com>
To:	linux-kernel@...r.kernel.org
Subject: PCI device memory bar access issue

There has one MV64460 on my board, which contains 2 PCI buses: PCI0 and 
PCI1.
PCI0 contains a transparent bridge. A PCI device locates behind the 
transparent
bridge. The PCI device has 2 memory bars. When I read on memory bar0, it 
returns
correct data. However, 0xffffffff returns from memory bar1.

I dump config space of the PCI device and find everything seems ok.

PCI_VENDOR_ID:       0x000010ee
PCI_DEVICE_ID:       0x00000300
PCI_COMMAND:         0x00000086
PCI_STATUS:          0x00000a00
PCI_CLASS_REVISION:  0x0b400000
PCI_CACHE_LINE_SIZE: 0x0000ff00
PCI_BASE_ADDRESS_0:  0x80800008
PCI_SPACE_SIZE_0:    0xfffff008
PCI_BASE_ADDRESS_1:  0x80801008
PCI_SPACE_SIZE_1:    0xfffff008
PCI_BASE_ADDRESS_2:  0x00000000
PCI_SPACE_SIZE_2:    0x00000000
PCI_BASE_ADDRESS_3:  0x00000000
PCI_SPACE_SIZE_3:    0x00000000
PCI_BASE_ADDRESS_4:  0x00000000
PCI_SPACE_SIZE_4:    0x00000000
PCI_BASE_ADDRESS_5:  0x00000000
PCI_SPACE_SIZE_5:    0x00000000

Thanks in advance for any suggestions.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/