[okl4-developer] Device Core

[Lukas HANEL]

Hi

I am currently porting drivers to the iguana driver framework. During
this I have yet some problems in understanding:

 * Driver servers take resource descriptions from the
elfweaver/machines.py file. They request the resources and make use of
the driver. However, there is also the device core, which seems to do
similar stuff: Allocating/requesting resources, providing virtual
devices. Is this a redundancy in e.g. the pxa platform, or is this a
requirement?

 * Can you document the interface for timer drivers? I have analysed the
pxa platforms and think it might be the following interface:
  * get_ticks() shall return the current time with the highest possible
precision.
  * timeout() shall program the timer to fire an interrupt at the
specified time.
  * device_interrupt_impl() shall return 1, when a timeout expired.
Is this right?

 * Are there any test cases for the vtimer, vserial, vrtc servers? I am
currently using the drivers example. But this example expects all the 3
servers to be already working. I would like to port and understand them
one after the other. Is it the right way to start with the timer server?

 * More a general understanding question: When I have several devices
with the same functionality, would I use them with the same server, or
one server per device?
Example: A multiple timer unit with one interrupt for 4 timers?

 * Bug: images and weaver.xml get not regenerated on
plat/tools/machine.py changements of device resources.

Thanks for sharing your experience,
Lukas Hänel