On Tue, Mar 13, 2012 at 10:57 AM, Jiri Svoboda <[email protected]> wrote: > Let's first look at the overall architecture, instead. In the end you > probably want to have some >'time server' which provides current time to applications upon request. >The time server probably combines multiple sources of information / time >sources, >depending on what's available (e.g. CMOS, timer interrupt, tick register).
This is probably the best solution, a completely generic time server and a bunch of separate hw specific drivers. When an application executes the time() function a request will be sent via IPC to the time server and the latter will reply with the current time, if I got it right. >> <jermar> not so sure rtc needs to be a char device > That would probably make no sense. :) Can't help but notice that everytime Jakub says "I'm not so sure about it" what he really means is "I'm *damn* sure about it". > You could prototype this without DDF and then, eventually, > split some part that talks to the CMOS to a DDF driver. Yes, it makes sense. -- -------------------- Maurizio Lombardi _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
