Yes, exactly.

If you need to handle timer interrupts as well, the irq handler capalility for that irq number will need to be passed to the other task.

Cheers,
Anna.

On 30/06/2016 9:08 am, Norrathep Rattanavipanon wrote:
I see. Thanks for the info.

So by default, the root task has complete control over physical address containing gpt data.
And if I want to use the gpt inside a different task, the root task has to pass its capability to that task.
Without that, any non-root task wouldnt be able to access it.

Am I understanding the timer's capability access control correctly?

Oak

On Tue, Jun 28, 2016 at 8:39 PM, Norrathep Rattanavipanon <nrattana@uci.edu> wrote:
Thanks Anna. 

We are looking for a way to get timestamp (wall clock) that can be used in the userland for authenticating an incoming message from remote server. 

I see that the real-time clock driver is not implemented yet but an accurate timer would do the job too.

So any recommendation on which timer implementation to use?

Thanks,
Oak


On Tue, Jun 28, 2016 at 5:17 PM, Norrathep Rattanavipanon <nrattana@uci.edu> wrote:
Hi,

I was wondering if there's any real time clock implementation for I.MX6 in sel4.

And if there isnt any, what would be the best way to use a timer in sel4 (since I saw many implementations of those)?
through sel4platsupport_get_default_timer?

Best,
Oak

--
Norrathep (Oak) Rattanavipanon
M.S. in Computer Science
University of California - Irvine



--
Norrathep (Oak) Rattanavipanon
M.S. in Computer Science
University of California - Irvine



--
Norrathep (Oak) Rattanavipanon
M.S. in Computer Science
University of California - Irvine


_______________________________________________
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel


-- 

Anna Lyons
Kernel engineer / PhD Student
DATA61 | CSIRO
E anna.lyons@nicta.com.au 
www.data61.csiro.au
 
CSIRO's Digital Productivity business unit and NICTA have joined forces to create digital powerhouse Data61
 



The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.