[okl4-developer] interrupt manager

[Carl van Schaik]

Hi,

Jorge Torres wrote:
>
> Ok, now, porting the pistachio/platform/pxa/include/plat/intctrl.h to 
> pistachio/platform/pc99/include/plat/intctrl.h (even dou knowing very 
> little about pc99 internals :) )
>
> I have a few questions (for now):
>
> is there somewhere something like #if defined(CONFIG_SUBPLAT_PXA255)
> for PC99, something like #ifdef PC99, how can I tell if its being 
> compiled for PC99?
Currently there is no subplatform support for PC99. PC99, EFI etc should 
probably be different platforms? I'm not sure how best to divide it up.
You will see CONFIG_PLAT_PC99 or CONFIG_PLAT_EFI defined.
>
> or where would be the best place to put (if correct):
>
> #ifndef CONFIG_EFI
> #define PC99
> #endif
That stuff should be configured via the build system. You can set it up 
in tools/machine.py I think there are already platform PC99 and EFI defined.

regards,
Carl
>
> On 5/14/07, *Carl van Schaik* < carl at ok-labs.com 
> <mailto:carl at ok-labs.com>> wrote:
>
>     Hi Jorge,
>
>     There is a global class already which could be used for this which
>     other
>     architectures use. I guess this is where the code should be.
>
>     ie:
>     pistachio/platform/generic/include/plat/intctrl-apic.h
>     pistachio/platform/generic/include/plat/intctrl-pic.h
>
>     should add a method similar to register_interrupt_handler() in
>     pistachio/platform/pxa/include/plat/intctrl.h but with ia32 specific
>     arguments.
>
>     regards,
>     Carl
>
>     Jorge Torres wrote:
>     > Hi okl4.org <http://okl4.org> <http://okl4.org <http://okl4.org>>,
>     >
>     >     > on this elegant irq interrupts handler registration
>     proposed  on
>     >     OKL4
>     >     > (irq_manager.register(hwirq, #, FUNCTION)), what is it
>     there to do?
>     >     I'm not an ia32 person, but I guess what they where after
>     was a class
>     >     that handled the irq related stuff (ie irq_manager). A
>     method of the
>     >     class would then be used to do the appropriate IDT etc
>     manipulation
>     >     stuff. I guess that they would want the irq manager to
>     handle multiple
>     >     levels of interrupt controllers and different hardware types.
>     >
>     >
>     > Carl, again excuse my ignorance; I don't know a thing about other
>     > architectures, but shouldn't an interrupt manager class be a global
>     > solution?
>     >
>     > Thanks again,
>     >
>     > Jorge
>     >
>
>