Difference between revisions of "Talk:OS InnerWait ms"

From WikiPrizm
Jump to navigationJump to search
m (formatting)
 
Line 6: Line 6:
 
** I wasn't dreaming, Ashbad experimented and found out it wouldn't work as expected for values above approximately 1000 ms ( http://www.cemetech.net/forum/viewtopic.php?p=169468#169468 ). I'd like to know an exact value though (if one exists, of course), so hopefully I will not forget to test it one day, and update this article. --[[User:Gbl08ma|Gbl08ma]] ([[User talk:Gbl08ma|talk]]) 19:13, 2 December 2014 (EST)
 
** I wasn't dreaming, Ashbad experimented and found out it wouldn't work as expected for values above approximately 1000 ms ( http://www.cemetech.net/forum/viewtopic.php?p=169468#169468 ). I'd like to know an exact value though (if one exists, of course), so hopefully I will not forget to test it one day, and update this article. --[[User:Gbl08ma|Gbl08ma]] ([[User talk:Gbl08ma|talk]]) 19:13, 2 December 2014 (EST)
 
*** I bet is has something to do with the valid range of numbers for the ticks to wait in the TMU.  -- [[User:Ahelper|Ahelper]] ([[User talk:Ahelper|talk]]) 19:16, 2 December 2014 (EST)
 
*** I bet is has something to do with the valid range of numbers for the ticks to wait in the TMU.  -- [[User:Ahelper|Ahelper]] ([[User talk:Ahelper|talk]]) 19:16, 2 December 2014 (EST)
 +
**** I did some tests on the emulator and found out that past 2000 ms, it kind of wraps around, i.e 2100 ms will hold execution for 100 ms. I also found out this syscall doesn't show the busy indicator as I thought. --[[User:Gbl08ma|Gbl08ma]] ([[User talk:Gbl08ma|talk]]) 17:08, 3 December 2014 (EST)

Latest revision as of 18:08, 3 December 2014

Missing Info

What's the range of accepted values?

Ahelper (talk) 19:03, 2 December 2014 (EST)

  • I think I read somewhere that it wouldn't behave very nicely for high values, like above 0.5 s or 1 s, can't quite remember, I might be making things up even. I will confirm and update this. --Gbl08ma (talk) 19:13, 2 December 2014 (EST)
    • I wasn't dreaming, Ashbad experimented and found out it wouldn't work as expected for values above approximately 1000 ms ( http://www.cemetech.net/forum/viewtopic.php?p=169468#169468 ). I'd like to know an exact value though (if one exists, of course), so hopefully I will not forget to test it one day, and update this article. --Gbl08ma (talk) 19:13, 2 December 2014 (EST)
      • I bet is has something to do with the valid range of numbers for the ticks to wait in the TMU. -- Ahelper (talk) 19:16, 2 December 2014 (EST)
        • I did some tests on the emulator and found out that past 2000 ms, it kind of wraps around, i.e 2100 ms will hold execution for 100 ms. I also found out this syscall doesn't show the busy indicator as I thought. --Gbl08ma (talk) 17:08, 3 December 2014 (EST)