From: Rajan Rai <Rajan.Rai@ingenient.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "Gala Kumar K.-galak" <kumar.gala@freescale.com>,
Liu Dave-r63238 <DaveLiu@freescale.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: PCI driver on EB8347
Date: Sun, 13 Aug 2006 00:31:31 -0400 [thread overview]
Message-ID: <44DEAB23.10404@ingenient.com> (raw)
In-Reply-To: <D9682BD5-FBDF-4D6C-BC82-6EF375DB6F46@kernel.crashing.org>
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
>
>
prev parent reply other threads:[~2006-08-13 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 0:49 PCI driver on EB8347 rajan rai
2006-08-11 3:40 ` Liu Dave-r63238
2006-08-11 9:15 ` rajan rai
2006-08-11 12:42 ` Kumar Gala
2006-08-12 12:34 ` Rajan Rai
2006-08-12 13:54 ` Kumar Gala
2006-08-12 16:07 ` rajan rai
2006-08-13 4:31 ` Rajan Rai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44DEAB23.10404@ingenient.com \
--to=rajan.rai@ingenient.com \
--cc=DaveLiu@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).