[okl4-developer] v2 driver with multiple memory ranges in okl4 3.0

[Gabi Voiculescu]

Hello.

I need to map into my v2 drivers multiple noncontiguous physical memory sections to properly program the particular peripherals on my machine. The (imediate) goal here is to run the ktest suite on my platform in okl4 3.

I need to map the SFR for the peripheral plus 2x 4k SFRs to program an additional Interrupt Controller.

On Okl4 2.1.0 there was an error in importing multiple memory ranges into the final image. Using multiple range entries defined in memory_xxx array in machines.py caused a compilation bug. 
At the time my fix was to have:
only added one range from the platform machines.py  used iguana interface functions: memsection_create_user() and hardware_back_memsection()to map in the additional memory ranges required, directly in my v2 driverI am now searching for the best solution to fulfill the same need (of mapping more, non-contiguous physical memory ranges), in my v2 drivers in order to be okl4 3+ compatible.

Can anyone give me an advice?

Thank you,
Gabi Voiculescu



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20090629/99d7a2cf/attachment.htm