Subject: Re: Pegasos port status
To: =?ISO-8859-1?Q?Jorge_Acereda_Maci=E1?= <jacereda@gmail.com>
From: Matt Thomas <matt@3am-software.com>
List: port-ofppc
Date: 07/17/2006 17:35:24
Jorge Acereda Maciá wrote:
> Jochen Kunz wrote:
>> On Mon, 17 Jul 2006 21:22:35 +0200
>> Jorge Acereda Maciá <jacereda@gmail.com> wrote:
>>
>>
>>> OFW also provides interrupt handling.
>>
>> How? AFAIK OFW provides interrupt mapping information via the properties
>> of device nodes. But there is no generic interrupt interface. (E.g. OFW
>> calls OS back if a device has signaled an interrupt or the like.) That
>> is why port ofppc runs so slow. All OFW device drivers use polling.
> 
> Hmmm... I thought there was a proposal to allow setting interrupt
> callbacks, but I've been searching for it without success. So probably
> it doesn't exist :-)

If OFW implements RAS (from CHRP), then that would make things implementation
independent.
-- 
Matt Thomas                     email: matt@3am-software.com
3am Software Foundry              www: http://3am-software.com/bio/matt/
Cupertino, CA              disclaimer: I avow all knowledge of this message.