From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ingenient.com (unknown [63.87.52.245]) by ozlabs.org (Postfix) with ESMTP id 97E0567B73 for ; Fri, 11 Aug 2006 11:04:30 +1000 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6BCE0.0E463295" Subject: PCI driver on EB8347 Date: Thu, 10 Aug 2006 19:49:52 -0500 Message-ID: <4DA89577C33E194ABEBC978921E858541B8E38@exchange.ingenient.net> From: "rajan rai" To: Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C6BCE0.0E463295 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have written PCI driver which works fine along with MPC8347 = and two PCI card connected in a single PCI bus. When I try to = communicate same PCI card using PCI bridge ( PCI2050B ), Linux does = detect PCI card on Secondary bus but same driver doesn't work !!!! =20 Do I need to enable support for second PCI host = controller at kernel level to make it work? Or I need to do something = else ? I tried compiling PPC-linux kernel after enabling = CONFIG_85xx_PCI2 kernel doesn't compile it gives me error while = compiling "arch/ppc/syslib/ppc83xx_setup.c" Kernel version I'm using is = 2.6.13. ****** Board along with which PCI card works ************ lspci -v /demo # lspci -v 00:1b.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01) Flags: bus master, medium devsel, latency 128, IRQ 21 Memory at 9fc00000 (32-bit, prefetchable) [size=3D4M] Memory at 9f000000 (32-bit, non-prefetchable) [size=3D8M] I/O ports at 3ffffff0 [size=3D16] Capabilities: [40] Power Management version 2 00:1c.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01) Flags: bus master, medium devsel, latency 128, IRQ 18 Memory at 9ec00000 (32-bit, prefetchable) [size=3D4M] Memory at 9e000000 (32-bit, non-prefetchable) [size=3D8M] I/O ports at 3fffffe0 [size=3D16] Capabilities: [40] Power Management version 2 ****** Board along with which PCI card doesn't work ************ lspci -v PCI devices found: Bus 0, device 17, function 0: Class 0604: PCI device 104c:ac28 (rev 2). Bus 1, device 1, function 0: Class 0000: PCI device 104c:9065 (rev 1). Master Capable. Latency=3D128. Prefetchable 32 bit memory at 0x9fc00000 [0x9fffffff]. Non-prefetchable 32 bit memory at 0x9f000000 [0x9f7fffff]. I/O at 0xfff0 [0xffff]. Bus 1, device 2, function 0: Class 0000: PCI device 104c:9065 (rev 1). Master Capable. Latency=3D128. Prefetchable 32 bit memory at 0x9ec00000 [0x9effffff]. Non-prefetchable 32 bit memory at 0x9e000000 [0x9e7fffff]. I/O at 0xffe0 [0xffef]. Any help would be appreciated I'm running out of = ideas what to do next !!!!!!!! Regards, -Rajan Rai ------_=_NextPart_001_01C6BCE0.0E463295 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable PCI driver on EB8347

        I have = written PCI driver which works fine along with MPC8347 and two PCI card = connected in a single PCI bus. When I try to communicate same PCI card = using PCI bridge ( PCI2050B ), Linux does detect PCI card on Secondary = bus but same driver doesn't work !!!!
      
            &= nbsp;    Do I need to enable support for second PCI host = controller at kernel level to make it work? Or I need to do something = else ? I tried compiling PPC-linux kernel after enabling = CONFIG_85xx_PCI2 kernel doesn't compile it gives me error while = compiling "arch/ppc/syslib/ppc83xx_setup.c" Kernel version I'm = using is 2.6.13.


****** Board along with which PCI card works ************
lspci -v
/demo # lspci -v
00:1b.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01)
        Flags: bus master, medium = devsel, latency 128, IRQ 21
        Memory at 9fc00000 (32-bit, = prefetchable) [size=3D4M]
        Memory at 9f000000 (32-bit, = non-prefetchable) [size=3D8M]
        I/O ports at 3ffffff0 = [size=3D16]
        Capabilities: [40] Power = Management version 2

00:1c.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01)
        Flags: bus master, medium = devsel, latency 128, IRQ 18
        Memory at 9ec00000 (32-bit, = prefetchable) [size=3D4M]
        Memory at 9e000000 (32-bit, = non-prefetchable) [size=3D8M]
        I/O ports at 3fffffe0 = [size=3D16]
        Capabilities: [40] Power = Management version 2


****** Board along with which PCI card doesn't work ************
lspci -v
PCI devices found:
  Bus  0, device  17, function  0:
    Class 0604: PCI device 104c:ac28 (rev 2).
  Bus  1, device   1, function  0:
    Class 0000: PCI device 104c:9065 (rev 1).
      Master Capable.  Latency=3D128.
      Prefetchable 32 bit memory at 0x9fc00000 = [0x9fffffff].
      Non-prefetchable 32 bit memory at = 0x9f000000 [0x9f7fffff].
      I/O at 0xfff0 [0xffff].
  Bus  1, device   2, function  0:
    Class 0000: PCI device 104c:9065 (rev 1).
      Master Capable.  Latency=3D128.
      Prefetchable 32 bit memory at 0x9ec00000 = [0x9effffff].
      Non-prefetchable 32 bit memory at = 0x9e000000 [0x9e7fffff].
      I/O at 0xffe0 [0xffef].

            &= nbsp;        Any help would be = appreciated I'm running out of ideas what to do next !!!!!!!!

Regards,
-Rajan Rai

------_=_NextPart_001_01C6BCE0.0E463295-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from de01egw01.freescale.net (de01egw01.freescale.net [192.88.165.102]) by ozlabs.org (Postfix) with ESMTP id 9EB7C67B5E for ; Fri, 11 Aug 2006 13:40:23 +1000 (EST) Received: from de01smr01.freescale.net (de01smr01.freescale.net [10.208.0.31]) by de01egw01.freescale.net (8.12.11/de01egw01) with ESMTP id k7B4wh9D004317 for ; Thu, 10 Aug 2006 22:58:43 -0600 (MDT) Received: from zch01exm21.fsl.freescale.net (zch01exm21.ap.freescale.net [10.192.129.205]) by de01smr01.freescale.net (8.13.1/8.13.0) with ESMTP id k7B3eIpW014974 for ; Thu, 10 Aug 2006 22:40:20 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: PCI driver on EB8347 Date: Fri, 11 Aug 2006 11:40:17 +0800 Message-ID: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> In-Reply-To: <4DA89577C33E194ABEBC978921E858541B8E38@exchange.ingenient.net> From: "Liu Dave-r63238" To: "rajan rai" , "Gala Kumar K.-galak" Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Rajan> I have written PCI driver which works fine along with MPC8347 and two PCI Rajan> card connected in a single PCI bus. When I try to communicate same PCI card Rajan> using PCI bridge ( PCI2050B ), Linux does detect PCI card on Secondary bus=20 Rajan> but same driver doesn't work !!!! PCI interrupt for secondary bus set up properly? =20 Rajan> Do I need to enable support for second PCI host controller at kernel level to=20 Rajan>make it work? Or I need to do something else ? I tried compiling PPC-linux kernel Rajan> after enabling CONFIG_85xx_PCI2 kernel doesn't compile it gives me error while=20 Rajan>compiling "arch/ppc/syslib/ppc83xx_setup.c" Kernel version I'm using is 2.6.13. Why you enable CONFIG_85xx_PCI2 in kernel? It is for 85xx, but you are using 8347 processor. Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ingenient.com (unknown [63.87.52.245]) by ozlabs.org (Postfix) with ESMTP id 822E067B6C for ; Fri, 11 Aug 2006 19:18:02 +1000 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6BD26.AF0945B9" Subject: RE: PCI driver on EB8347 Date: Fri, 11 Aug 2006 04:15:26 -0500 Message-ID: <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> References: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> From: "rajan rai" To: "Liu Dave-r63238" , "Gala Kumar K.-galak" Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C6BD26.AF0945B9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 I'm using polling mechanism and not interrupts in = my driver. Although I'm not using polling I see strange behavior When I = do lspci -v I don't see any interrupts being allocated to PCI device = behind PCI bridge !!!! But when I use same card directly on primary bus = I do see interrupt being allocated to PCI device. Any advise why IRQ's = being not allocated in case its attached to PCI bridge ? =20 Do I need to take care of any extra = configuration in case of PCI card is attached to PCI bridge ? =20 Yaa you are correct I shouldn't use CONFIG_85xx_PCI2 =20 Thanks, -Rajan ________________________________ From: Liu Dave-r63238 [mailto:DaveLiu@freescale.com] Sent: Thu 8/10/2006 10:40 PM To: rajan rai; Gala Kumar K.-galak Cc: linuxppc-embedded@ozlabs.org Subject: RE: PCI driver on EB8347 Rajan> I have written PCI driver which works fine along with MPC8347 and two PCI Rajan> card connected in a single PCI bus. When I try to communicate same PCI card Rajan> using PCI bridge ( PCI2050B ), Linux does detect PCI card on Secondary bus Rajan> but same driver doesn't work !!!! PCI interrupt for secondary bus set up properly? =20 Rajan> Do I need to enable support for second PCI host controller at kernel level to Rajan>make it work? Or I need to do something else ? I tried compiling PPC-linux kernel Rajan> after enabling CONFIG_85xx_PCI2 kernel doesn't compile it gives me error while Rajan>compiling "arch/ppc/syslib/ppc83xx_setup.c" Kernel version I'm using is 2.6.13. Why you enable CONFIG_85xx_PCI2 in kernel? It is for 85xx, but you are using 8347 processor. Dave ------_=_NextPart_001_01C6BD26.AF0945B9 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= RE: PCI driver on EB8347=0A= =0A= =0A=
=0A=
 
=0A=
          &nbs= p;           =0A= I'm using polling mechanism and not interrupts in my = driver. Although I'm =0A= not using polling I see strange behavior When I do lspci -v I don't = see any =0A= interrupts being allocated to PCI device behind PCI bridge !!!! But when = I use =0A= same card directly on primary bus I do see interrupt being allocated to = PCI =0A= device. Any advise why IRQ's being not allocated in case its = attached =0A= to PCI bridge ?
=0A=
 
=0A=
          &nbs= p;            = ;       =0A= Do I need to take care of any extra configuration in case of PCI card is =0A= attached to PCI bridge ?
=0A=
 
=0A=
Yaa you are = correct I =0A= shouldn't use CONFIG_85xx_PCI2
=0A=
 
=0A=
Thanks,
=0A=
-Rajan
=0A=

=0A=
=0A= From: Liu Dave-r63238 =0A= [mailto:DaveLiu@freescale.com]
Sent: Thu 8/10/2006 10:40 =0A= PM
To: rajan rai; Gala Kumar K.-galak
Cc: =0A= linuxppc-embedded@ozlabs.org
Subject: RE: PCI driver on =0A= EB8347

=0A=

=0A=

Rajan>        I = have =0A= written PCI driver which works fine along with
MPC8347 and two =0A= PCI
Rajan> card connected in a single PCI bus. When I try to =0A= communicate
same PCI card
Rajan> using PCI bridge ( PCI2050B ), = Linux =0A= does detect PCI card on
Secondary bus
Rajan> but same driver = doesn't =0A= work !!!!

PCI interrupt for secondary bus set up =0A= properly?
     
Rajan>   = ;     =0A= Do I need to enable support for second PCI host controller
at kernel = level =0A= to
Rajan>make it work? Or I need to do something else ? I tried =0A= compiling
PPC-linux kernel
Rajan> after enabling = CONFIG_85xx_PCI2 =0A= kernel doesn't compile it gives
me error while
Rajan>compiling =0A= "arch/ppc/syslib/ppc83xx_setup.c" Kernel version I'm
using is =0A= 2.6.13.

Why you enable CONFIG_85xx_PCI2 in kernel? It is for = 85xx, but =0A= you are
using 8347 =0A= processor.

<snip>

Dave

=0A= =0A= =0A= ------_=_NextPart_001_01C6BD26.AF0945B9-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nommos.sslcatacombnetworking.com (nommos.sslcatacombnetworking.com [67.18.224.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 849CC67B62 for ; Fri, 11 Aug 2006 22:42:27 +1000 (EST) In-Reply-To: <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> References: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <94857DB0-ABC7-4AA5-BE5B-1CBEAA09D906@kernel.crashing.org> From: Kumar Gala Subject: Re: PCI driver on EB8347 Date: Fri, 11 Aug 2006 07:42:19 -0500 To: rajan rai Cc: "Gala Kumar K.-galak" , Liu Dave-r63238 , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Aug 11, 2006, at 4:15 AM, rajan rai wrote: > > I'm using polling mechanism and not > interrupts in my driver. Although I'm not using polling I see > strange behavior When I do lspci -v I don't see any interrupts > being allocated to PCI device behind PCI bridge !!!! But when I use > same card directly on primary bus I do see interrupt being > allocated to PCI device. Any advise why IRQ's being not allocated > in case its attached to PCI bridge ? > > Do I need to take care of any extra > configuration in case of PCI card is attached to PCI bridge ? You need to make sure that the pci_map_irq/mpc83xx_map_irq function handles the right swizziling for the P2P bridge for your setup. If you are just connected directly its pretty straight forward. However IRQ assignment behind the bridge can be very board specific and so you need to make sure that the code is doing the right think for you. What ever strangeness do you see from lspci? - k From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ingenient.com (unknown [63.87.52.245]) by ozlabs.org (Postfix) with ESMTP id 02D0B67BDB for ; Sat, 12 Aug 2006 22:35:29 +1000 (EST) Message-ID: <44DDCAB8.80106@ingenient.com> Date: Sat, 12 Aug 2006 08:34:00 -0400 From: Rajan Rai MIME-Version: 1.0 To: Kumar Gala Subject: Re: PCI driver on EB8347 References: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> <94857DB0-ABC7-4AA5-BE5B-1CBEAA09D906@kernel.crashing.org> In-Reply-To: <94857DB0-ABC7-4AA5-BE5B-1CBEAA09D906@kernel.crashing.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: "Gala Kumar K.-galak" , Liu Dave-r63238 , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Thanks IRQ problem is resolved. As pointed out it was problem with IRQ IDSEL mapping. Mapping needs to be different on Eval board I'm using and our custom design. But my driver is still not working on our custom design. PCI device doesn't receive any messages from MPC8347 on our custom design mother board which uses pci-bridge where as it works fine on Eval board which doesn't use PCI bridge. I guess problem lies at the kernel level and not the driver. Any tips apart from IDSEL IRQ settings at kernel level what else I need to change when I move from 1 mother board to another. My PCI devices do get base address 0 and 1 allocated properly by the OS. But when I try to write any messages on those addresses PCI device doesn't see them Regards, -Rajan Kumar Gala wrote: > > On Aug 11, 2006, at 4:15 AM, rajan rai wrote: > >> >> I'm using polling mechanism and not interrupts >> in my driver. Although I'm not using polling I see strange behavior >> When I do lspci -v I don't see any interrupts being allocated to PCI >> device behind PCI bridge !!!! But when I use same card directly on >> primary bus I do see interrupt being allocated to PCI device. Any >> advise why IRQ's being not allocated in case its attached to PCI >> bridge ? >> >> Do I need to take care of any extra >> configuration in case of PCI card is attached to PCI bridge ? > > You need to make sure that the pci_map_irq/mpc83xx_map_irq function > handles the right swizziling for the P2P bridge for your setup. If > you are just connected directly its pretty straight forward. However > IRQ assignment behind the bridge can be very board specific and so you > need to make sure that the code is doing the right think for you. > > What ever strangeness do you see from lspci? > > - k > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nommos.sslcatacombnetworking.com (nommos.sslcatacombnetworking.com [67.18.224.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id C45D5679E0 for ; Sat, 12 Aug 2006 23:54:49 +1000 (EST) In-Reply-To: <44DDCAB8.80106@ingenient.com> References: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> <94857DB0-ABC7-4AA5-BE5B-1CBEAA09D906@kernel.crashing.org> <44DDCAB8.80106@ingenient.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Kumar Gala Subject: Re: PCI driver on EB8347 Date: Sat, 12 Aug 2006 08:54:45 -0500 To: Rajan Rai Cc: "Gala Kumar K.-galak" , Liu Dave-r63238 , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Aug 12, 2006, at 7:34 AM, Rajan Rai wrote: > > > Thanks IRQ problem is resolved. As pointed out it was > problem with IRQ IDSEL mapping. Mapping needs to be different on > Eval board I'm using and our custom design. But my driver is still > not working on our custom design. PCI device doesn't receive any > messages from MPC8347 on our custom design mother board which uses > pci-bridge where as it works fine on Eval board which doesn't use > PCI bridge. > > I guess problem lies at the kernel level > and not the driver. Any tips apart from IDSEL IRQ settings at > kernel level what else I need to change when I move from 1 mother > board to another. My PCI devices do get base address 0 and 1 > allocated properly by the OS. But when I try to write any messages > on those addresses PCI device doesn't see them Is the bridge getting configured correctly? An lspci output would be helpful from your system with the P2P bridge. - kumar From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ingenient.com (unknown [63.87.52.245]) by ozlabs.org (Postfix) with ESMTP id F285F679FB for ; Sun, 13 Aug 2006 02:09:44 +1000 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6BE29.5D790361" Subject: RE: PCI driver on EB8347 Date: Sat, 12 Aug 2006 11:07:09 -0500 Message-ID: <4DA89577C33E194ABEBC978921E858541B8E3E@exchange.ingenient.net> References: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> <94857DB0-ABC7-4AA5-BE5B-1CBEAA09D906@kernel.crashing.org> <44DDCAB8.80106@ingenient.com> From: "rajan rai" To: "Kumar Gala" Cc: "Gala Kumar K.-galak" , Liu Dave-r63238 , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C6BE29.5D790361 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Kumar, Here is lspci -v from my P2P system. In case you have any = suggestion do let me know. I appreciate your help 00:11.0 PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 02) = (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=3D00, secondary=3D01, subordinate=3D01, = sec-latency=3D0 I/O behind bridge: 0000f000-0000ffff Memory behind bridge: 9e000000-9fffffff Prefetchable memory behind bridge: = 000000009df00000-000000009df00000 Capabilities: [dc] Power Management version 2 01:01.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01) Flags: bus master, 66Mhz, medium devsel, latency 128, IRQ 18 Memory at 9fc00000 (32-bit, prefetchable) [size=3D4M] Memory at 9f000000 (32-bit, non-prefetchable) [size=3D8M] I/O ports at 3ffffff0 [size=3D16] Capabilities: [40] Power Management version 2 01:02.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01) Flags: bus master, 66Mhz, medium devsel, latency 128, IRQ 19 Memory at 9ec00000 (32-bit, prefetchable) [size=3D4M] Memory at 9e000000 (32-bit, non-prefetchable) [size=3D8M] I/O ports at 3fffffe0 [size=3D16] Capabilities: [40] Power Management version 2 Regards -Rajan Rai -----Original Message----- From: Kumar Gala [mailto:galak@kernel.crashing.org] Sent: Sat 8/12/2006 8:54 AM To: rajan rai Cc: Liu Dave-r63238; Gala Kumar K.-galak; linuxppc-embedded@ozlabs.org Subject: Re: PCI driver on EB8347 =20 On Aug 12, 2006, at 7:34 AM, Rajan Rai wrote: > > > Thanks IRQ problem is resolved. As pointed out it was =20 > problem with IRQ IDSEL mapping. Mapping needs to be different on =20 > Eval board I'm using and our custom design. But my driver is still =20 > not working on our custom design. PCI device doesn't receive any =20 > messages from MPC8347 on our custom design mother board which uses =20 > pci-bridge where as it works fine on Eval board which doesn't use =20 > PCI bridge. > > I guess problem lies at the kernel level =20 > and not the driver. Any tips apart from IDSEL IRQ settings at =20 > kernel level what else I need to change when I move from 1 mother =20 > board to another. My PCI devices do get base address 0 and 1 =20 > allocated properly by the OS. But when I try to write any messages =20 > on those addresses PCI device doesn't see them Is the bridge getting configured correctly? An lspci output would be =20 helpful from your system with the P2P bridge. - kumar ------_=_NextPart_001_01C6BE29.5D790361 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: PCI driver on EB8347

Kumar,

         Here is lspci -v from = my P2P system. In case you have any suggestion do let me know. I = appreciate your help

00:11.0 PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 02) = (prog-if 00 [Normal decode])
        Flags: bus master, 66Mhz, = medium devsel, latency 0
        Bus: primary=3D00, = secondary=3D01, subordinate=3D01, sec-latency=3D0
        I/O behind bridge: = 0000f000-0000ffff
        Memory behind bridge: = 9e000000-9fffffff
        Prefetchable memory behind = bridge: 000000009df00000-000000009df00000
        Capabilities: [dc] Power = Management version 2

01:01.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01)
        Flags: bus master, 66Mhz, = medium devsel, latency 128, IRQ 18
        Memory at 9fc00000 (32-bit, = prefetchable) [size=3D4M]
        Memory at 9f000000 (32-bit, = non-prefetchable) [size=3D8M]
        I/O ports at 3ffffff0 = [size=3D16]
        Capabilities: [40] Power = Management version 2

01:02.0 Non-VGA unclassified device: Texas Instruments: Unknown device = 9065 (rev 01)
        Flags: bus master, 66Mhz, = medium devsel, latency 128, IRQ 19
        Memory at 9ec00000 (32-bit, = prefetchable) [size=3D4M]
        Memory at 9e000000 (32-bit, = non-prefetchable) [size=3D8M]
        I/O ports at 3fffffe0 = [size=3D16]
        Capabilities: [40] Power = Management version 2


Regards
-Rajan Rai


-----Original Message-----
From: Kumar Gala [mailto:galak@kernel.crashing.or= g]
Sent: Sat 8/12/2006 8:54 AM
To: rajan rai
Cc: Liu Dave-r63238; Gala Kumar K.-galak; = linuxppc-embedded@ozlabs.org
Subject: Re: PCI driver on EB8347


On Aug 12, 2006, at 7:34 AM, Rajan Rai wrote:

>
>
>          Thanks IRQ = problem is resolved. As  pointed out it was 
> problem with IRQ IDSEL mapping. Mapping needs to be different = on 
> Eval board I'm using and our custom design. But my driver is = still 
> not working on our custom design. PCI device doesn't receive = any 
> messages from MPC8347 on our custom design mother board which = uses 
> pci-bridge where as it works fine on Eval board which doesn't = use 
> PCI bridge.
>
>           &nb= sp;           &nbs= p; I guess problem lies at the kernel level 
> and not the driver. Any tips apart from IDSEL IRQ settings = at 
> kernel level what else I need to change when I move from 1 = mother 
> board to another.  My PCI  devices do get base address 0 = and 1 
> allocated properly by the OS. But when I try to write any = messages 
> on those addresses PCI device doesn't see them

Is the bridge getting configured correctly?  An lspci output would = be 
helpful from your system with the P2P bridge.

- kumar

------_=_NextPart_001_01C6BE29.5D790361-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ingenient.com (unknown [63.87.52.245]) by ozlabs.org (Postfix) with ESMTP id 6B32667C1B for ; Sun, 13 Aug 2006 14:32:59 +1000 (EST) Message-ID: <44DEAB23.10404@ingenient.com> Date: Sun, 13 Aug 2006 00:31:31 -0400 From: Rajan Rai MIME-Version: 1.0 To: Kumar Gala Subject: Re: PCI driver on EB8347 References: <995B09A8299C2C44B59866F6391D2635018CA7@zch01exm21.fsl.freescale.net> <4DA89577C33E194ABEBC978921E858541B8E3B@exchange.ingenient.net> <94857DB0-ABC7-4AA5-BE5B-1CBEAA09D906@kernel.crashing.org> <44DDCAB8.80106@ingenient.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: "Gala Kumar K.-galak" , Liu Dave-r63238 , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Kumar, Liu I was able to resolve problem. Problem was in PCI card firmware and not in Linux Kernel or driver. Thanks for your help. Regards, -Rajan Kumar Gala wrote: > > On Aug 12, 2006, at 7:34 AM, Rajan Rai wrote: > >> >> >> Thanks IRQ problem is resolved. As pointed out it was >> problem with IRQ IDSEL mapping. Mapping needs to be different on Eval >> board I'm using and our custom design. But my driver is still not >> working on our custom design. PCI device doesn't receive any messages >> from MPC8347 on our custom design mother board which uses pci-bridge >> where as it works fine on Eval board which doesn't use PCI bridge. >> >> I guess problem lies at the kernel level and >> not the driver. Any tips apart from IDSEL IRQ settings at kernel >> level what else I need to change when I move from 1 mother board to >> another. My PCI devices do get base address 0 and 1 allocated >> properly by the OS. But when I try to write any messages on those >> addresses PCI device doesn't see them > > Is the bridge getting configured correctly? An lspci output would be > helpful from your system with the P2P bridge. > > - kumar > >