[okl4-developer] devicecore

[Geoffrey Lee]

On Wed, Jul 09, 2008 at 03:51:54PM +0200, Oliver Mayer-Buschmann wrote:
> Hi,
> 

Hi Oliver

> during my evaluation of the OKL Driver-Framework and its virtual servers
> I've found the interface "devicecore.idl4", and under platform, there
> exists for each supported platform a module device_core.c.
> 
> In the OKL documentation "Using A Virtual Device" this interface is used
> in the sample code (4.3.2 Initializing the Device).
> 
> 1. I'm wondering if this code is still in use or if it's obsolete.

The build system has taken over the responsbility of the devicecore,
and hence the devicecore is no longer used.


> 
> 2. What happened to the methods
> -virtual_<XX>_factory_create
> -virtual_<XX>_add_memsection
> -virtual_<XX>_register_control_block
> -device_create


Devices are now created statically.  To use a device, you specify
the name of the device in the client's build script fragment.

For example, in vserial, the following is present in SConscript:

env.required_vdevs["vserial"] = (["vtimer"])

This means that the vserial program relies vtimer.  The reason
why this is here is because the l4kdb_uart relies on the
vtimer program.  Have a look at the l4kdb_uart driver in drivers/
to get a simple of example of how to use the timer driver.


> 
> 3. Does there exist any documentation how the driver instances are
> created and mapped to the virtual servers? I'm especially interested in
> detailed information of how the build system handles this.

The PDF tutorial on the wiki is slightly out of date.  We are aware
of this and we are in the process of updating the documents to match
with the current implementation of the OKL4 software.


> 
> 4. I've found several indications for the existance of a name server and
> a MTD-device driver in OKL4. Where is this code?

Please note that the name server is now obsolete.  The preferred way
to obtain names is via the environment variable feature in OKL4.  We
currently do not yet have a usable mtd driver for OKL4 2.1.

> 
> 5. How shall the connection to virtual devices be established from
> wombat?
> 

OK Linux acts as a client of the virtual device servers.  In OK Linux,
we write a stub driver that communicates with the virtual device.

> Thank you!
> 
> Oliver

	-gl


> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer


--