Re: OEM Adaption Layer and OAL stubs

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

SetLocalTime() and GetLocalTime() will probably do what you want clock-wise.
Why would you *want* to use some kind of low-level access to get to the
clock?

Paul T.

"Garratt" <Christian.H.Mikkelsen@xxxxxxxxx> wrote in message
news:eibJgC4FGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
> So what you guys are really saying is that I should use KernelIOControl()
> with the IOCTL_XXX parameters to set/get
> the RTC and reboot the machine?
> Ive tried it out and it seems to work fine :-D. Thx a mil.
>
> However I have two more questions
>
> 1. Is it possible to write an app that directly calls the OEMXX() or
> OEMIOCONTROL methods and then deploy it on
> the target OR are the OEMxxx() calls restricted to be used only
> internally by the kernel somehow?
> (Cant seem to link the stuff even when i add the missing nkintr.h,
> gives me unresolved error)
> Should I be able to call the OEM functions?
> Note. I have verified that the OEMfunctions I call are implemented
> in the VIA bsp. Might I be missing the correct .lib?
>
> 2. Have I gotton this right.
> KernelIOControl -> calls OAL functions (Which actually are the OEM
> function build into the kernel at image creation time).
> The OAL will most likely call the OEMIOCONTROL function which will
> then map to the correct OEM function, however this depends
> on how VIA has made the implementation.
>
> Again if you have any links about the actual structure of this hiearchy I
> would be gratefull.
>
> Best regards
> Christian
>
>
> "Garratt" <Christian.H.Mikkelsen@xxxxxxxxx> wrote in message
> news:u3hmZTcFGHA.140@xxxxxxxxxxxxxxxxxxxxxxx
>> Hey
>>
>> Currently im using the latest VIA cepc twister bsp for my target.
>> Among other things I want to be able to call the realtime clock to get
>> and set the clock and call methods to reset (hard or soft) the
>> system.
>> Now when i look at the bsp setup i can see that the
>> Platfrom/common/src/x86 has been added to the via bsp
>> /platform/via/src/kernel/x86/commen/etc...
>> and looking in the src files i can see that the methods has been modified
>> by via to match the platform, which is to be expected :-D.
>>
>> Now my question is how do I call these methods in my software? Ive
>> allready build the sdk, but when looking at microsoft ce site they
>> allways
>> refer the method calls to use "nk.h" and "nk.lib", which gives me loads
>> of errors when i attemp to compile and link.
>> Im most certainly missing out on an important issue about how to call
>> these methods (might there be some VIA specific nk.h file ???),
>> can anyone clearify for me how to do this (what to link to and what
>> headers to use?) or more importantly supply me with information about how
>> this OEM specific methods actually are used to create a bsp so that I may
>> understand the process better.
>>
>> When trying to understand how it works to, I look at the help and always
>> ends up reading about the "How to develop an OEM Adaption Layer" and
>> "Creating stubs for OAL functions".
>> Can anyone help me clearify or send a link that can explain the structure
>> and procedure?
>>
>> Best regards
>> Christian
>>
>>
>>
>>
>
>


.

Relevant Pages

  • Re: OEM Adaption Layer and OAL stubs
    ... function build into the kernel at image creation time). ... > Currently im using the latest VIA cepc twister bsp for my target. ... > this OEM specific methods actually are used to create a bsp so that I may ... > Can anyone help me clearify or send a link that can explain the structure ...
    (microsoft.public.windowsce.embedded)
  • Filesystem - Windows CE 6.0 - Data Abort!!
    ... BSP System Configuration: ... ARM CLOCK = 266000000 Hz ... Old or invalid version stamp in kernel structures - starting clean! ... It is hanging in File System driver. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: POSIX leap seconds versus the current NTP behaviour
    ... As long as kernel support is available, ntpd does nothing about leap seconds except compile a consensus from server leap bits, Autokey protocol or leapseconds file whether a leap event is pending or not. ... It does assume the kernel clock is stepped back one second at the epoch of the event, but the routine that actually reads the clock for consumers is constrained to never set the clock back and to insure that every reading advances the clock by no lees than one unit of resolution, typically one nanosecond with interpolation. ... constrains how the clock can be adjusted (though not the ultimate precision of an adjustment, ...
    (comp.protocols.time.ntp)
  • Time Drift Compensation on Linux Clusters
    ... While working on a Linux cluster with kernel version 2.4.27 we've ... for this problem which is based on the Pentium's TSC clock. ... Following is a detailed description of the problem and the fix, ... The number of interrupt per second is defined by ...
    (Linux-Kernel)
  • Re: ntp discipline of local time?
    ... The kernel discipline is almost identical to the daemon discipline with the exception that the fancy code to combine the PLL and FLL near the Allan intercept is absent. ... like the clock state machine and poll-adjust algorithm continue in the daemon. ... The phase error is probably being filtered using an IIR filter, and that is what you are seeing, and also the mechanism ntpd uses to stop wandering off if it stops receiving updates (the frequency measurement error can produce unbounded phase errors, but the phase error correction is bounded). ...
    (comp.protocols.time.ntp)