OpenQNX :: The QNX Community Portal

Oct 07, 2008 - 11:53 AM
Google
  Web openqnx.com   
     Create an account Home · Submit News · QNX Forums · QNX Download · Search   
_
Main Menu
Who's Online
There are 46 unlogged users and 3 registered users online.

You can log-in or register for a user account here.

This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.
View previous topic Printable version Log in to check your private messages View next topic
Author Message
Pusik Park
Post subject: What is the meaning of _NTO_INTR_SPARE at the startup_intrin  PostPosted: Feb 18, 2008 - 08:48 AM
Guest





Hello.



My 32-bit ARM9 RISC SoC has just 1 interrupt controller with 29 interrupt
sources.

If I understood the cascaded vector's meaning well, I doesn't need cascaded
vectors.



Is it right ?



const static struct startup_intrinfo intrs[] = {

{ _NTO_INTR_CLASS_EXTERNAL, // vector
base

32, //
number of vectors

_NTO_INTR_SPARE, //
cascade vector

0, //
CPU vector base

0, //
CPU vector stride

0, //
flags

{ INTR_GENFLAG_LOAD_SYSPAGE, 0, &interrupt_id_jaguar2
},

{ INTR_GENFLAG_LOAD_SYSPAGE |
INTR_GENFLAG_LOAD_INTRMASK, 0, &interrupt_eoi_jaguar2 },

&interrupt_mask_jaguar2, // mask callout

&interrupt_unmask_jaguar2, // unmask callout

0, // config
callout

}



The upper source code is my startup_intrinfo but I think its source code has
the problem.

I think that there is some proper value for a cascade vector instead of
_NTO_INTR_SPACE.

Actually, I didn't understand the meaning of the cascade vector.



Please help me.



Best regards.



Pusik.
 
   
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.
View previous topic Printable version Log in to check your private messages View next topic
Powered by PNphpBB2 © 2003-2007 The PNphpBB Group
Credits
All logos and trademarks in this site are property of their respective owners. The comments are property of their posters.
Powered by OpenQNX: The QNX Community Portal Site
QNX and the QNX logo are registered trademarks of QNX Software Systems.