Re: [alliance-iosk] IOSK LM

[Stefano.Costa@italtel.it]

Ramon van Handel wrote:

> No, it's in the CK access library, formally part of the KL but for now
> under the CK tree (see CK/lib/architecture/I80X86/syscalls.c).  The
> function starts with 'CK' because its implementation is in the CK, though
> the actual function CKresourceAlloc() is really the stub, not the function
> itself.  You can use CKresourceAlloc(), that's what it's for.

Ok, I'll change that.

> LMerror isn't documented in your IOSK LM spec... I don't see it in the code
> either.  If this isn't implemented yet, ignore my problems in the other
> message.

no, it's not in my code, but was discussed some time ago in iosk list. Anyway I'll
implemet it as I have written, if you agree.

> It is VERY interesting, I like it too :).  But one must place priorities
> somewhere... ;)

Yes, but when you are in love with someone or something, you are not so rational ;)

> >Question: under CK tree there is ELF.
>
> Do you mean the documentation ?  You can move that.

Oh, well, I have only seen the name, and thinked was also code! We should move
that....

> What are you talking about ?  There is not ELF *code* in the CK dir, only
> documentation.  The dynamic loader belongs in the KL, not in the SL.

Ok, see above.

> ... but hard to test on linux... you can't really surpass the linux
> terminal code.  You're better off writing LMs for modules that you can turn
> off in linux... until the CK can support the IOSK.

Yes, for that you have to put LM code inside kernel.

Stefano


-
Alliance-IOSK:	http://iosk.allos.org/
Archive:	http://humbolt.nl.linux.org/lists/