Hi Robert, 

you are not alone in the timertick handler if you are using the new tcpip-stack. 
Io-pkt does the same.
So every timer-tick the cpu run's  through the kernel, io-pkt proccess and  your process. Depending of the actual load 
of your system, the ppc405 executes  many exeptions, to map the pages for your irq-handlers in.
Perhaps you have a good reason for this approach, but I can't see any reason for the io-pkt networking. Well, in the 
past I got no official statement according the io-pkt tick handler. This is my 3rd try.

Regards 
Michael

> Thanks Colin, it's now working.
> 
> robert
> 
> -----Original Message-----
> From: Colin Burgess [mailto:community-noreply@qnx.com] 
> Sent: Thursday, August 27, 2009 12:49 PM
> To: ostech-core_os
> Subject: Re: Sharing PIT interrupt on PPC405
> 
> The timer interrupt vector is SYSPAGE_ENTRY(qtime)->intr - you can pass
> that value to InterruptAttach.
> 
> Robert D'Attilio wrote:
> > Hi:
> > 
> > Wondering if it is at all possible to attach my own interrupt handler
> to the PIT on a PPC405EP in addition to the already attached handler
> that manages the system ticks. If so, would anyone have some example
> code on how to set this up i.e. I'm not sure what interrupt vector
> number to use in the call to interruptAttach as it's not listed as one
> of the 30  interrupt sources in the PPC405 manual.
> > 
> > thanks
> > robert
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 
> > OSTech
> > http://community.qnx.com/sf/go/post36796
> > 
> 
> -- 
> cburgess@qnx.com
> 
> 
> 
> _______________________________________________
> 
> OSTech
> http://community.qnx.com/sf/go/post36807