Re: [MiNT] Fwd: Re: marathon,was:Egale

["Helmut Karlowski" <helmut.karlowski@ish.de>]

Jo Even Skarstein wrote:

> > I think the slb has its own apid, which differs from that of the caller.
>
> If that's the case then there's a problem. Such a behaviour (SLB itself
> being an AES client) means that you can't use the AES cleanly from a SLB!
>
> - appl_init() from the SLB will register the SLB as an AES client. But
> there can't be more than one AES client per process, so this SLB is no
> longer shared.
> - If a function in a SLB calls the AES and the AES sees this as a call
>  from the SLB process, then the SLB must also call appl_init()...
>
> So you're stuck ;)

Not me - marathon ;-)

> The AES must treat calls from a SLB function as if they're coming from the
> process that's calling this SLB function. If not, then SLB's can't work as
> intended.

So the AES should test for every trap if it comes from an slb, and if so use the callers apid? I guess it's
easier and much cleaner to implement a proper interface in the slb (like other libs do).


-Helmut