Re: Nesting interrupts with ARM core
From: Steve Maillet \(eMVP\) (nospam1_at_EntelechyConsulting.com)
Date: 02/24/05
- Next message: Steve Maillet \(eMVP\): "Re: Using Embedded VisualC to debug a driver"
- Previous message: momalley: ""unidentified usb device" on CE 5.0"
- In reply to: Jeo: "Nesting interrupts with ARM core"
- Next in thread: Jeo: "Re: Nesting interrupts with ARM core"
- Reply: Jeo: "Re: Nesting interrupts with ARM core"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Feb 2005 08:35:01 +1300
The ARM core has only a single interrupt vector. However virtually ALL CPUs
that have the ARM core have some sort of interrupt controller that you can
quickly read to determine the first level interrupt sources. (You can call
those IRQs) Normally the OEMInterruptHandler in the OAL will read the
interrupt controller to determine the highest priority pending Interrupt
request and return the SYSINTR_ ID for that device.
-- Steve Maillet EmbeddedFusion www.EmbeddedFusion.com smaillet at EmbeddedFusion dot com
- Next message: Steve Maillet \(eMVP\): "Re: Using Embedded VisualC to debug a driver"
- Previous message: momalley: ""unidentified usb device" on CE 5.0"
- In reply to: Jeo: "Nesting interrupts with ARM core"
- Next in thread: Jeo: "Re: Nesting interrupts with ARM core"
- Reply: Jeo: "Re: Nesting interrupts with ARM core"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|