Hi! I am trying to access a custom PCI device on a Walnut Rev. D system
running Hard Hat Linux Rev. 1.2 with Montavista kernel snapshot
01.04.12. The following code is beeing executed in the probe function of
a kernel module and works well on Linux 2.4.2/Intel but returns useless
values on PowerPC.
### begin code ###
unsigned long linux_addr_start, linux_addr_end, val;
u32 config_addr;
pdev = pci_find_device(0x10ee, 0x4030, pdev);
if (NULL == pdev)
return(-1);
if (pci_enable_device(pdev))
return(-1);
linux_addr_start = pci_resource_start(pdev, 0);
linux_addr_end = pci_resource_end(pdev, 0);
pci_read_config_dword(pdev, PCI_BASE_ADDRESS_0, &config_addr);
printk("Found %s\n", pdev->name);
printk("pci_resource_start=%lx\n", linux_addr_start);
printk("pci_resource_end=%lx\n", linux_addr_end);
printk("PCI_BASE_ADDRESS_0=%lx\n", config_addr);
IOAddress = ioremap(config_addr, 0xffff);
if (IOAddress) {
val = readl(IOAddress + 0xb000);
printk("read %lx at remapped PCI_BASE_ADDRESS_0\n",
val);
iounmap(IOAddress);
}
IOAddress = ioremap(linux_addr_start, 0xffff);
if (IOAddress) {
val = readl(IOAddress + 0xb000);
printk("read %lx at remapped pci_resource_start\n",
val);
iounmap(IOAddress);
}
### end code ###
### begin i686 result ###
Found PCI device 10ee:4030 (Xilinx, Inc.)
pci_resource_start=e2000000
pci_resource_end=e200ffff
PCI_BASE_ADDRESS_0=e2000000
read fffffff0 at remapped PCI_BASE_ADDRESS_0
read fffffff0 at remapped pci_resource_start
### end i686 result ###
### begin ppc result ###
Found PCI device 10ee:4030 (Xilinx, Inc.)
pci_resource_start=10000000
pci_resource_end=0
PCI_BASE_ADDRESS_0=ffff0000
read 0 at remapped PCI_BASE_ADDRESS_0
Machine Check: PLB0 bear= 0x1000b000 acr= 0x00000000 besr=
0x0c000000
Machine Check: PLB0 to OPB bear= 0x80401000 besr0= 0x00000000 besr1=
0x00000000
Data Machine Check in kernel mode.
Oops: machine check, sig: 7
NIP: C3004160 XER: 20000000 LR: C3004148 SP: C1E69DA0 REGS: c1e69cf0
TRAP: 0200
MSR: 00009230 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c1e68000[30] 'insmod' Last syscall: 128
last math 00000000 last altivec 00000000
GPR00: C3011000 C1E69DA0 C1E68000 C3006000 00000000 00000F45 00000015
C013E000
GPR08: 00000C30 C3016000 C3006000 C02F3000 C013EC30 1001F130 100ABCB0
00000000
GPR16: 100A4C50 10010000 7FFFDF98 00000000 00009230 01E69E80 C1E69DE8
C1ECB2E0
GPR24: 00000008 C1E69E4C 10022B38 0000004C FFFFFFEA 00000000 10000000
C3000000
Call backtrace:
C3004148 C30044E8 C0013B98 C00026B4 10010000 10003360 100039F4
0FF055B8 00000000
Bus error
### end ppc result ###
Any hints/suggestions?
Regards
Tom
Zehetbauer Thomas wrote:
>
> Hi! I am trying to access a custom PCI device on a Walnut Rev. D system
> running Hard Hat Linux Rev. 1.2 with Montavista kernel snapshot
> 01.04.12. The following code is beeing executed in the probe function of
> a kernel module and works well on Linux 2.4.2/Intel but returns useless
> values on PowerPC.
>
> ### begin code ###
> unsigned long linux_addr_start, linux_addr_end, val;
> u32 config_addr;
>
> pdev = pci_find_device(0x10ee, 0x4030, pdev);
> if (NULL == pdev)
> return(-1);
use pci_register_driver or pci_module_init not pci_find_device
> if (pci_enable_device(pdev))
> return(-1);
> linux_addr_start = pci_resource_start(pdev, 0);
> linux_addr_end = pci_resource_end(pdev, 0);
> pci_read_config_dword(pdev, PCI_BASE_ADDRESS_0, &config_addr);
> printk("Found %s\n", pdev->name);
> printk("pci_resource_start=%lx\n", linux_addr_start);
> printk("pci_resource_end=%lx\n", linux_addr_end);
> printk("PCI_BASE_ADDRESS_0=%lx\n", config_addr);
> IOAddress = ioremap(config_addr, 0xffff);
bug: calling ioremap with config_addr value directly from PCI BAR
register. You should mask the value. However, it is irrelevant:
linux_addr_start make config_addr unnecessary.
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
Zehetbauer Thomas writes:
> Hi! I am trying to access a custom PCI device on a Walnut Rev. D system
> running Hard Hat Linux Rev. 1.2 with Montavista kernel snapshot
> 01.04.12. The following code is beeing executed in the probe function of
> a kernel module and works well on Linux 2.4.2/Intel but returns useless
> values on PowerPC.
What kernel version is this? We have fixed a few bugs in the PCI code
on PPC lately.
> ### begin ppc result ###
> Found PCI device 10ee:4030 (Xilinx, Inc.)
> pci_resource_start=10000000
> pci_resource_end=0
> PCI_BASE_ADDRESS_0=ffff0000
This looks bogus, it looks like the firmware hasn't assigned an
address to this device. Current PPC kernels should assign a
reasonable address in this case - this is something that has been
fixed since 2.4.2 came out.
Paul.