View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002098 | fsvybrid_Linux | Kernel | public | 2014-02-10 16:19 | 2014-04-07 15:25 |
| Reporter | Keller | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | fsvybrid-V1.1 | ||||
| Target Version | fsvybrid-V1.2 | Fixed in Version | fsvybrid-V1.2 | ||
| Summary | 0002098: Sleep functions on Vybrid only work with mulitples of 10ms | ||||
| Description | Distributor/Customer reports that all sleeping functions on Vybrid only work with multiples of 10ms, which is rather coarse. | ||||
| Steps To Reproduce | Distri Mail: Apparently everytime they use a sleep function in Linux, the minimum time that my thread will sleep is exactly a multiple of 10 milliseconds. So, if they try to sleep 8 ms, it will sleep 10 ms. If I try to sleep 11 ms, it will sleep 20 ms. This affect very much their application in a negative way. Even non real-time Linux has a clock resolution that is less than 1 ms. I have the feeling that this is somehow related with the option of the kernel related to PIT (Programmable Interrupt Timer), but this is just an hypothesis. | ||||
| Additional Information | Check if this has to do with the PIT timing. In Timesys patch linux-3.0-vybrid-ts2.8 there was a modification called: Add Global Timer support to fix High Resolution Timer functionality Maybe this is the solution. In fact the real global_timer.c was added with linux-3.0-vybrid-ts2.9, so both patches have to be considered. | ||||
| Forum Link | |||||
