linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brian Waite <bwaite@irobot.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Marvell MV64360 interrupt question
Date: Mon, 12 Sep 2005 08:56:23 -0400	[thread overview]
Message-ID: <200509120856.24096.bwaite@irobot.com> (raw)
In-Reply-To: <1126292945.21092.26.camel@excalibur.timesys.com>

On Friday 09 September 2005 3:09 pm, Walter L. Wimer III wrote:
> Thinking about this some more, I think the cascade mechanism I suggested
> earlier is backwards.  Architecturally, I think it makes more sense to
> define a platform-specific function like boardXYZ_get_irq() in
> boardXYZ_setup.c that knows all of the idiosyncrasies of the board and
> calls whatever standard PIC libraries it needs in order to do the right
> thing.  Then we set ppc_md.get_irq = boardXYZ_get_irq;
>
> I looked around, and lo and behold, the Radstone PPC7D already "stole"
> my idea.  :-)  :-)
>
>
Yes, the syslib case in the general case. You can easily override the 
get_irq() routine for your own platform to match a priority scheme you 
desire. 

Thanks
Brian

  reply	other threads:[~2005-09-12 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 17:31 Marvell MV64360 interrupt question Walter L. Wimer III
2005-09-09 19:09 ` Walter L. Wimer III
2005-09-12 12:56   ` Brian Waite [this message]
2005-09-09 19:27 ` Dale Farnsworth
2005-09-09 19:52   ` Walter L. Wimer III
2005-09-09 20:20   ` Walter L. Wimer III
2005-09-09 20:49     ` Dale Farnsworth
2005-09-09 21:18       ` Mark A. Greer
2005-09-12 13:05         ` Brian Waite

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=200509120856.24096.bwaite@irobot.com \
    --to=bwaite@irobot.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).