Hi Xi,
AEP's got renamed to Notification's. So in this example seL4_TCB_BindAEP
got renamed to seL4_TCB_BindNotification.
Adrian
On Thu 11-Feb-2016 1:08 PM, HyperNewbie wrote:
I'm trying to update RefOS.
I see seL4_TCB_BindAEP is gone; is there anything similar to replace
this? Or do we have to use a separate thread to emulate this behaviour?
- Xi
On 10 February 2016 at 17:33, Kevin Elphinstone
<[email protected]
<mailto:[email protected]>> wrote:
RefOS was a student project that is now no longer actively
maintained. It would make an ideal community or personal project
for somebody to pick up, albeit one with a steep initial learning
curve.
Yes, you are hitting API changes. The best way forward would be to
port RefOS to the newer API. Downgrading would be a temporary
solution at best.
-Kevin
Assoc. Prof. Kevin Elphinstone, Trustworthy Systems
*DATA61 | CSIRO*
*E
*[email protected]<mailto:[email protected]>*T*+61
2 8306 0573 <tel:%2B61%202%208306%200573>
www.data61.csiro.au<http://www.data61.csiro.au/>
*CSIRO’s Digital Productivity business unit and NICTA have joined
forces to create digital powerhouse Data61*
cid:[email protected]
*From:*Devel [mailto:[email protected]
<mailto:[email protected]>] *On Behalf Of *Gapry Un
*Sent:* Sunday, 24 January 2016 9:31 PM
*To:* [email protected]
*Subject:* [seL4] Can not build RefOS
Dear all,
I follow the official step
(https://github.com/seL4/refos-manifest) to build RefOS and it
occurs the following error message.
In file included from
/home/chi-wai/Workspaces/microkernel/RefOS/libs/librefos/src/sync.c:16:0:
~/Workspaces/RefOS/stage/arm/imx31/include/refos/refos.h:73:1:
*error: unknown type name ‘uint32_t’*
~/Workspaces/RefOS/stage/arm/imx31/include/refos/refos.h:73:23:
*error: unknown type name ‘uint32_t’*
In file included from
/home/chi-wai/Workspaces/microkernel/RefOS/libs/librefos/src/sync.c:18:0:
~/Workspaces/RefOS/stage/arm/imx31/include/refos-util/cspace.h:44:72:
*error: unknown type name ‘uint32_t’*
~/Workspaces/RefOS/libs/librefos/src/sync.c: In function
‘sync_create_mutex’:
~/Workspaces/RefOS/libs/librefos/src/sync.c:49:5: /_warning_/:
‘seL4_Notify’ is deprecated (declared at
/home/chi-wai/Workspaces/microkernel/RefOS/stage/arm/imx31/include/sel4/deprecated.h:23):
use seL4_Signal [-Wdeprecated-declarations]
~/Workspaces/RefOS/libs/librefos/src/sync.c: In function
‘sync_acquire’:
~/Workspaces/RefOS/libs/librefos/src/sync.c:65:5: *error: invalid
initializer*
~/Workspaces/RefOS/libs/librefos/src/sync.c: In function
‘sync_release’:
~/Workspaces/RefOS/libs/librefos/src/sync.c:74:5: /_warning_/:
‘seL4_Notify’ is deprecated (declared at
/home/chi-wai/Workspaces/microkernel/RefOS/stage/arm/imx31/include/sel4/deprecated.h:23):
use seL4_Signal [-Wdeprecated-declarations]
make[1]: *** [src/sync.o] Error 1
make: *** [librefos] Error 2
Does RefOS use the old seL4 API ? If it is, which version I need
to downgrade?
Thanks for any help or suggestion,
Gapry.
https://gapry.wordpress.com/
------------------------------------------------------------------------
The information in this e-mail may be confidential and subject to
legal professional privilege and/or copyright. National ICT
Australia Limited accepts no liability for any damage caused by
this email or its attachments.
_______________________________________________
Devel mailing list
[email protected]
https://sel4.systems/lists/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
https://sel4.systems/lists/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
https://sel4.systems/lists/listinfo/devel
