[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [qiao <at80401@yahoo.com>] (fwd)



>From owner-rtl Wed Jun 20 23:52:14 2001
Received: from web10708.mail.yahoo.com (web10708.mail.yahoo.com [216.136.130.216])
	by hq.fsmlabs.com (8.11.2/8.11.2) with SMTP id f5L5qEe07243
	for <rtl@fsmlabs.com>; Wed, 20 Jun 2001 23:52:14 -0600
Message-ID: <20010621054604.30517.qmail@web10708.mail.yahoo.com>
Received: from [61.187.22.24] by web10708.mail.yahoo.com; Wed, 20 Jun 2001 22:46:04 PDT
Date: Wed, 20 Jun 2001 22:46:04 -0700 (PDT)
From: qiao <at80401@yahoo.com>
Subject: how to process shared interrupt?
To: rtl@fsmlabs.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


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 owner-rtl@fsmlabs.com -----