Thank you Martin.
The problem is, as you referred in your other mail.
So, if you're in the VMM, you can acces the RAM through this object. If you're in another component you would have to request the VMM to release the IO_MEM-Region to be able to allocate it through a new IO_MEM session.
Regards
Chirag Garg IIT Madras , Rise Lab
On Tue, May 5, 2015 at 1:43 PM, Martin Stein <martin.stein@...1...> wrote:
Hi Chirag,
On 05.05.2015 07:38, chirag garg wrote:
It gives me the following fault.
I/O memory [40000000,50000000) not available Local MMIO mapping failed! [init -> tz_vmm] C++ runtime: Genode::Parent::Service_denied
You can take this fault as a starting point by searching (e.g. via grep) for "I/O memory .* not available" in the repositories base and base-hw. Presumably, this will lead you to the code path that is responsible for allocating MMIO regions. From there, you might be able to trace back were your region gets "lost" and to whom.
Cheers, Martin
One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main