<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: PCI driver on EB8347</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Kumar,<BR>
<BR>
Here is lspci -v from my P2P system. In case you have any suggestion do let me know. I appreciate your help<BR>
<BR>
00:11.0 PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 02) (prog-if 00 [Normal decode])<BR>
Flags: bus master, 66Mhz, medium devsel, latency 0<BR>
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0<BR>
I/O behind bridge: 0000f000-0000ffff<BR>
Memory behind bridge: 9e000000-9fffffff<BR>
Prefetchable memory behind bridge: 000000009df00000-000000009df00000<BR>
Capabilities: [dc] Power Management version 2<BR>
<BR>
01:01.0 Non-VGA unclassified device: Texas Instruments: Unknown device 9065 (rev 01)<BR>
Flags: bus master, 66Mhz, medium devsel, latency 128, IRQ 18<BR>
Memory at 9fc00000 (32-bit, prefetchable) [size=4M]<BR>
Memory at 9f000000 (32-bit, non-prefetchable) [size=8M]<BR>
I/O ports at 3ffffff0 [size=16]<BR>
Capabilities: [40] Power Management version 2<BR>
<BR>
01:02.0 Non-VGA unclassified device: Texas Instruments: Unknown device 9065 (rev 01)<BR>
Flags: bus master, 66Mhz, medium devsel, latency 128, IRQ 19<BR>
Memory at 9ec00000 (32-bit, prefetchable) [size=4M]<BR>
Memory at 9e000000 (32-bit, non-prefetchable) [size=8M]<BR>
I/O ports at 3fffffe0 [size=16]<BR>
Capabilities: [40] Power Management version 2<BR>
<BR>
<BR>
Regards<BR>
-Rajan Rai<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Kumar Gala [<A HREF="mailto:galak@kernel.crashing.org">mailto:galak@kernel.crashing.org</A>]<BR>
Sent: Sat 8/12/2006 8:54 AM<BR>
To: rajan rai<BR>
Cc: Liu Dave-r63238; Gala Kumar K.-galak; linuxppc-embedded@ozlabs.org<BR>
Subject: Re: PCI driver on EB8347<BR>
<BR>
<BR>
On Aug 12, 2006, at 7:34 AM, Rajan Rai wrote:<BR>
<BR>
><BR>
><BR>
> Thanks IRQ problem is resolved. As pointed out it was <BR>
> problem with IRQ IDSEL mapping. Mapping needs to be different on <BR>
> Eval board I'm using and our custom design. But my driver is still <BR>
> not working on our custom design. PCI device doesn't receive any <BR>
> messages from MPC8347 on our custom design mother board which uses <BR>
> pci-bridge where as it works fine on Eval board which doesn't use <BR>
> PCI bridge.<BR>
><BR>
> I guess problem lies at the kernel level <BR>
> and not the driver. Any tips apart from IDSEL IRQ settings at <BR>
> kernel level what else I need to change when I move from 1 mother <BR>
> board to another. My PCI devices do get base address 0 and 1 <BR>
> allocated properly by the OS. But when I try to write any messages <BR>
> on those addresses PCI device doesn't see them<BR>
<BR>
Is the bridge getting configured correctly? An lspci output would be <BR>
helpful from your system with the P2P bridge.<BR>
<BR>
- kumar<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>