Re: [MiNT] Kernel modules loader (was: Re: XaAES and appl_init())

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

David Gálvez, 27.02.2013 11:12:00:

> 2013/2/26 Helmut Karlowski <helmut.karlowski@ish.de>:
> > In the end maybe it's possible to use xaloader for appl_init as  
> > suggested by
> > you but that's more expensive as I don't know yet how to pass the apid  
> > to
> > XaAES and would possibly require to exchange xaloader by anyone. Also I  
> > have
> > plans to get rid of xaloader completely but that's very vague.
>
> Helmut, could you explain please what you have in mind regarding the  
> xaloader?
>
> I think we should discuss a mid or long term solution for loading
> kernel modules. Something like a universal loader for any km module,
> that could take care of dependencies between modules too, and unload
> them at runtime.

Yes - that was the first idea.

> I suspect ozk had something in mind when the actual km implementation
> was done. For sure I read somewhere that the idea was to get rid of
> the different modules types (xdd, xfs, xid, etc...) and to have only

Also an old plan by many people.

> one kind (km). I don't know if this is realistic now as a lot of work
> should been done yet to accomplish this.

First I'll write a generic km-loader.
The first km that uses it will be audiodev which is an xdd currently.

Then see how it's possible to let the loader manage several modules.

Then if possible integrate this loader into the kernel.

But as I said: All very uncertain.

--
Helmut Karlowski