From: agnel juni <junijoseph@yahoo.co.in>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: PCI IRQ -MPC8540
Date: Tue, 16 Jan 2007 23:20:34 +0000 (GMT) [thread overview]
Message-ID: <20070116232034.40662.qmail@web8414.mail.in.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2506 bytes --]
Hello all:
I would like to understand if there is a way to program the PCI interrupt pin register of MPC8540. I did look for this in the datasheet, but couldn't find any positive answer.
Currently, I am working in a set-up where MPC8540 is an agent, plugged into the PC host.
I couldn't get an IRQ for the card when plugged in some PCI slots, whereas in one of the slots I do see a non-zero value.
It would be great if you could help me understand the issue.
I am sorry if the question is inapporpriate in the group. I am desperate to solve the issue.
Thanks for any help.
J.Joseph
----- Original Message ----
From: Kumar Gala <galak@kernel.crashing.org>
To: Wang Matthew-R59995 <Qi.W@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Sent: Wednesday, 18 October, 2006 6:54:24 PM
Subject: Re: Linuxppc-embedded Digest, Vol 26, Issue 36
On Oct 18, 2006, at 8:10 PM, Wang Matthew-R59995 wrote:
> Hi Kumar,
>
> Actually I do many trials about it. Vxwerks Bootrom is smaller than
> U-Boot. The key difference between Bootrom and U-boot is that some
> source code of Bootrom is invisible to the users.
>
> Actually the rfi instruction which I point out is the first rfi
> instruction of Linux PowerPC bringup.
>
> Before that, it's TLB entry invalidation and temp TLB entry mapping.
>
> I check MMU setting carefully before coming Linux Kernel.
>
> I just want to know if other guys met similar scenario like me. I
> don't
> need the precise answer, just overall suggestion about it because I
> understand that not everyone has the same bootloader of mine, that
> bootloader is actually a customized bootloader.
I understand that, thus I was asking what exact problem you were
seeing to try and help.
> Anyway thank you.
>
> R9 point to LR register, mask the high 20 bit of r9 and send to r7,
> and
> then add 24, which means stride 6 instructions for rfi instruction
> execution.
>
> Of course, rfi can switch the TLB entry, both the previous TLB
> entry and
> the temp TLB entry point to the same physical address.
>
> I've checked it.
I know what the code does, I wrote it :)
- kumar
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
[-- Attachment #2: Type: text/html, Size: 3262 bytes --]
next reply other threads:[~2007-01-16 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 23:20 agnel juni [this message]
2007-01-17 0:29 ` PCI IRQ -MPC8540 Steve Iribarne (GMail)
2007-01-17 1:29 ` Kumar Gala
[not found] <20070117015413.28659.qmail@web8407.mail.in.yahoo.com>
2007-01-17 1:56 ` Kumar Gala
2007-01-17 9:34 ` Jin Zhengxiong-R64188
-- strict thread matches above, loose matches on Subject: below --
2007-01-22 20:27 agnel juni
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=20070116232034.40662.qmail@web8414.mail.in.yahoo.com \
--to=junijoseph@yahoo.co.in \
--cc=galak@kernel.crashing.org \
--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).