Here is -rc3, the dust is settling down now. For this release, we
have been working on the following issues:
o Generic 64-bit arithmetic support [Gilles]
o More powerpc 32/64 merging [Heikki]
o Native API updates [Jan, Gilles, me]
o POSIX API updates [Gilles]
o RTDM updates [Jan]
o Blackfin port
Jan Kiszka wrote:
Hi Dmitry,
Dmitry Adamushko wrote:
Hi Jan,
let's make yet another revision of the bits :
new XN_ISR_HANDLED == old XN_ISR_HANDLED + old XN_ISR_NO_ENABLE
ok.
new XN_ISR_NOENABLE == ~ old XN_ISR_ENABLE
ok.
new XN_ISR_PROPAGATE == XN_ISR_CHAINED
ok.
Just to make sure
N.B. Amongst other things, some thoughts about CHAINED with shared interrupts.
On 20/02/06, Anders Blomdell <[EMAIL PROTECTED]> wrote:
A number of questions arise:1. What happens if one of the shared handlers leaves the interrupt asserted,
returns NOENABLE|HANDLED and another return only HANDLE
Jan Kiszka wrote:
Hi Dmitry,
Dmitry Adamushko wrote:
Hi Jan,
let's make yet another revision of the bits :
new XN_ISR_HANDLED == old XN_ISR_HANDLED + old XN_ISR_NO_ENABLE
ok.
new XN_ISR_NOENABLE == ~ old XN_ISR_ENABLE
ok.
new XN_ISR_PROPAGATE == XN_ISR_CHAINED
ok.
Just to make sure
N.B. Amongst other things, some thoughts about CHAINED with shared interrupts.
On 20/02/06, Anders Blomdell <[EMAIL PROTECTED]> wrote:
A number of questions arise:1. What happens if one of the shared handlers leaves the interrupt asserted,
returns NOENABLE|HANDLED and another return only HANDLE
Here is -rc3, the dust is settling down now. For this release, we
have been working on the following issues:
o Generic 64-bit arithmetic support [Gilles]
o More powerpc 32/64 merging [Heikki]
o Native API updates [Jan, Gilles, me]
o POSIX API updates [Gilles]
o RTDM updates [Jan]
o Blackfin port
