From: "Mark.Zhan" <rongkai.zhan@windriver.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] Wind River 4KC PPMC Eval Board Support
Date: Wed, 10 May 2006 10:41:16 +0800 [thread overview]
Message-ID: <446152CC.6020904@windriver.com> (raw)
In-Reply-To: <20060509164127.GA10647@linux-mips.org>
Ralf Baechle wrote:
> On Sat, May 06, 2006 at 05:04:20PM +0800, Mark.Zhan wrote:
>
>> According to your comments, I re-create the patch. Hopefully, no line-wrapped problems:-)
>> Patch 1 and 2 in the original mails are concatenated into one patch in this mail.
>
> Well, this patch was still somewhat corrupt, a few spaces were missing
Huhh, I don't what's wrong with my thunderbird.
> but I was somehow able to talk git into taking it. So it's applied on
> the queue branch.
>
> Ralf
After looking into the changeset ac58afdfac792c0583af30dbd9eae53e24c78b,
I find what I want to do has been done by you:-)
For those MIPS32 boards which only use IRQ_CPU, I think, we can provide
a default plat_irq_dispatch() implemention, maybe like this:
asmlinkage plat_irq_dispatch(struct pt_regs *regs)
{
unsigned int pending = read_c0_status() & read_c0_cause();
int irq;
irq = ffs(pending >> 8) - 1;
return do_IRQ(irq, regs);
}
I this it will clean up more codes......
Best Regards,
Mark.Zhan
next prev parent reply other threads:[~2006-05-10 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 9:04 [PATCH 1/2] Wind River 4KC PPMC Eval Board Support Mark.Zhan
2006-05-09 16:41 ` Ralf Baechle
2006-05-10 2:41 ` Mark.Zhan [this message]
2006-05-10 15:32 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2006-05-05 15:42 Zhan, Rongkai
2006-05-05 15:42 ` Zhan, Rongkai
2006-05-05 16:07 ` Ralf Baechle
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=446152CC.6020904@windriver.com \
--to=rongkai.zhan@windriver.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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