Victor Yodaiken wrote:
>
> My belief is that shared interrupts are not very
useful for RT systems - does anyone
> think otherwise?
>
> If an interrupt is shared between RT and non RT
devices, the RT driver must do
>
> catch_interrupt:
> examine my device
> if interrupt is mine
> do regular handling
> else
> pend interrupt for Linux/BSD
> find the interrupting non-RT device
> clear device interrupt
> re-enable interrupts from this source
How to do this four step?
is there a function that pass the interrupt to non-RT linux kernel?
>
> The key point is that the RT driver needs to look at
all non-RT devices
> in order to clear the interrupt source.
> This is not too hard, but it seems not very RT.
I think ,in RT interrupt handler , check if the interrupt is it's own ,
if not ,pass it to non-RT linux to do other jobs, this will be almost RT.
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
----- End of forwarded message from [EMAIL PROTECTED] -----
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
