Ben Leslie

Please provide a sample image that demonstrates the problem; I don't have an iOS device.

I find the documentation ambiguous on that point as well. I think it does both?

Thanks for the replies Gerwin and Gernot. I guess I'm still confused. In terms of the `concepts` admitted into the design we appear to have: 1: A `capability address`; which...

Apologies; at this point I think I've split this initial issue into two related, but distinct discussions. Possibly should have been in Discourse not GitHub, but anyway. Pressing on here...

> Just referring to the seL4_Signal and error returning part here: > seL4_Signal is an alias of seL4_Send and is conventionally used only on notification objects. If you perform seL4_Call...

> A slightly more radical departure from the current API would be to say "everything is a syscall", not "everything is an IPC with the kernel". Then it would make...

> To @bennoleslie's question: call() is not just send();receive(), it does more, incl setting up the reply channel: the object you send to is not the object you receive from...

Further on the *what should the behaviour of seL4_Send on a null cap be* question. I again don't have a strong opinion (other than not 'nothing'), but I feel it...

That sounds like a great idea. Unfortunately I will not have the time to implement it, but more than willing to merge a pull-request that implements it.

I'd prefer to not merge as is, as I don't like breaking APIs. I'd suggest the one or both of the following: 1: Add a get_altitude() method. 2: Add a...