public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: terry <tqiu@neuros.com.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: where is the interrupt vectors?
Date: Thu, 24 Nov 2005 18:20:01 +0800	[thread overview]
Message-ID: <1132827601.2550.53.camel@PC6> (raw)
In-Reply-To: <OFBCAD8E28.98312CBF-ON482570C3.002B338F@uk.marconicomms.com>

yes, I make a mistake.
The CPU I used is ARM926ejs.I never look through other files.
May be there is other method I didn't know.

Thank you 

Terry

On Thu, 2005-11-24 at 15:53 +0800, KokHow Teh wrote:
> 
> >In message <1132812293.2550.20.camel@PC6> you wrote:
> >>
> >> Thank you for your reply ,but I think you misunderstood my question.
> 
> >No, it is you who does not understand.
> 
> >> What I said is the extern interrupts, and now I have know that U-BOOT is
> >> no support the interrupts, so it doesn't need the vectors.
> 
> >You are wrong. You can use interrupts in U-Boot. There is  even  code
> >in the examples directory which does so.
> 
> and here are the external interrupts:
> 
> ./74xx_7xx/interrupts.c:62:external_interrupt(struct pt_regs *regs)
> ./74xx_7xx/interrupts.c:64:     puts("external_interrupt (oops!)\n");
> ./74xx_7xx/start.S:122: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./mpc5xx/interrupts.c:75:void external_interrupt (struct pt_regs *regs)
> ./mpc5xx/start.S:208:   STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./mpc5xxx/interrupts.c:48:external_interrupt(struct pt_regs *regs)
> ./mpc5xxx/interrupts.c:50:      puts("external_interrupt (oops!)\n");
> ./mpc5xxx/start.S:206:  STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./mpc8220/interrupts.c:47:void external_interrupt (struct pt_regs *regs)
> ./mpc8220/interrupts.c:49:      puts ("external_interrupt (oops!)\n");
> ./mpc8220/start.S:167:  STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./mpc824x/interrupts.c:56:void external_interrupt (struct pt_regs *regs)
> ./mpc824x/start.S:218:  STD_EXCEPTION(EXC_OFF_EXTERNAL, ExtInterrupt, external_interrupt)
> ./mpc8260/interrupts.c:177:void external_interrupt (struct pt_regs *regs)
> ./mpc8260/start.S:277:  STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./mpc83xx/interrupts.c:54:void external_interrupt (struct pt_regs *regs)
> ./mpc83xx/start.S:219:  STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./mpc8xx/interrupts.c:68:void external_interrupt (struct pt_regs *regs)
> ./mpc8xx/start.S:222:   STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> ./nios/interrupts.c:103:void external_interrupt (struct pt_regs *regs)
> ./nios/traps.S:318: * The default handler passes control to external_interrupt(). So trap
> ./nios/traps.S:323: * external_interrupt(). This lets the underflow and overflow handlers
> ./nios/traps.S:398:     pfx     %hi(external_interrupt at h)
> ./nios/traps.S:399:     movi    %o1, %lo(external_interrupt at h)
> ./nios/traps.S:400:     pfx     %xhi(external_interrupt at h)
> ./nios/traps.S:401:     movhi   %o1, %xlo(external_interrupt at h)
> ./nios2/exceptions.S:83:        movhi   r3, %hi(external_interrupt)
> ./nios2/exceptions.S:84:        ori     r3, r3, %lo(external_interrupt)
> ./nios2/interrupts.c:121:void external_interrupt (struct pt_regs *regs)
> ./ppc4xx/interrupts.c:199:void external_interrupt(struct pt_regs *regs)
> ./ppc4xx/interrupts.c:222:} /* external_interrupt CONFIG_440GX */
> ./ppc4xx/interrupts.c:226:void external_interrupt(struct pt_regs *regs)
> ./ppc4xx/start.S:783:   STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users

  reply	other threads:[~2005-11-24 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24  7:53 [U-Boot-Users] Re: where is the interrupt vectors? KokHow Teh
2005-11-24 10:20 ` terry [this message]
     [not found] <20051124033401.309058900A@sc8-sf-spam1.sourceforge.net>
2005-11-24  6:04 ` terry
2005-11-24  7:47   ` Wolfgang Denk
2005-11-24  9:41     ` terry

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=1132827601.2550.53.camel@PC6 \
    --to=tqiu@neuros.com.cn \
    --cc=u-boot@lists.denx.de \
    /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