linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ben Warren <bwarren@qstreams.com>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 83xx: requesting external interrupts
Date: Thu, 10 May 2007 13:07:27 -0400	[thread overview]
Message-ID: <1178816847.9018.2.camel@saruman.qstreams.net> (raw)
In-Reply-To: <46434C1E.3020004@cambridgebroadband.com>

Alex,

Follow this thread...
http://marc.info/?l=linuxppc-embedded&m=116849062702002&w=2

On Thu, 2007-05-10 at 17:45 +0100, Alex Zeffertt wrote:
> Hi list,
> 
> I'm trying to port a driver from 2.6.11 to 2.6.21 and I'm stuck on the following line:
> 
> 	request_irq(MPC83xx_IRQ_EXT5, mpc832xemds_phy_interrupt, SA_SHIRQ, "pm5384", dev);
> 
> The first problem is that MPC83xx_IRQ_EXT5 is no longer defined.  If I hard code this to
> what I think is the right value (i.e. 21) then request_irq fails on insmod.
> 
> I obviously need to do something different now that ARCH=powerpc, but I can't find any
> examples of code which requests 83xx external interrupts.  Can anybody help?
> 
> TIA,
> 
> Alex
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2007-05-10 17:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 16:45 83xx: requesting external interrupts Alex Zeffertt
2007-05-10 17:07 ` Ben Warren [this message]
     [not found]   ` <46443784.3060600@cambridgebroadband.com>
2007-05-11 14:12     ` Ben Warren
2007-05-11 20:15       ` Kumar Gala
2007-05-11 20:29         ` Ben Warren
2007-05-11 20:37           ` Kumar Gala
2007-06-29 11:34       ` Joakim Tjernlund
2007-06-29 16:43         ` Ben Warren
2007-06-29 23:54         ` Andy Fleming
2007-06-30 14:02           ` Joakim Tjernlund

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=1178816847.9018.2.camel@saruman.qstreams.net \
    --to=bwarren@qstreams.com \
    --cc=ajz@cambridgebroadband.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).