- 11 1月, 2014 1 次提交
-
-
由 bernard 提交于
-
- 21 12月, 2013 2 次提交
-
-
由 Grissiom 提交于
Out side world is difficult to tell whethere there is dead thread remaining. If rt_thread_idle_excute only do one cleanup, it's hard to finish cleanups outside the idle thread. So let is loop and do all the cleanups in one call.
-
由 Grissiom 提交于
Out side world may be interested in whether the scheduler is locked or not. Provide an API to tell that.
-
- 19 10月, 2013 1 次提交
-
-
由 Grissiom 提交于
-
- 14 10月, 2013 1 次提交
-
-
由 Grissiom 提交于
Mutex has the idea of ownership, only the thread which owns the mutex can release it. So rt_mutex_release could only be called in thread context. Add a debug guard to it.
-
- 12 10月, 2013 1 次提交
-
-
由 Grissiom 提交于
Skip list is a "random" data structure that in high possibilities it would get O(log(N)) time complexity in inserting while the old list get O(N). Forthermore, when set RT_TIMER_SKIP_LIST_LEVEL to 1, it will just the same as the old double linked list, both in time and space complexity. Benchmarks shows that when RT_TIMER_SKIP_LIST_LEVEL is 3, the average time of random insertion of new timer is about 2 times faster than the old timer when there are 100 timers and 3 times faster when there are 200 timers. However, it restores the deprecated funcion rt_system_timer_init. BSPs must invoke it upon system startup.
-
- 11 10月, 2013 1 次提交
-
-
由 Grissiom 提交于
In thread context means: 1) the scheduler has been started; 2) not in interrupt context. It is more stronger than RT_DEBUG_NOT_IN_INTERRUPT. With this commit, you will catch the error on situations like taking mutex before scheduling instead of crashing on NULL pointer reference.
-
- 24 9月, 2013 1 次提交
-
-
由 wuyangyong 提交于
-
- 23 9月, 2013 1 次提交
-
-
由 Grissiom 提交于
vsnprintf is a common string function that could be used in many places. Using both vsnprintf in libc and vsnprintf in the RTT could make a bigger image. Moreover, if newlib is not enabled when compiling with GCC, referencing vsnprintf will lead to link error: .../arm-none-eabi/lib/armv7-ar/thumb/softfp/libc.a(lib_a-sbrkr.o): In function `_sbrk_r': sbrkr.c:(.text._sbrk_r+0xc): undefined reference to `_sbrk' collect2: error: ld returned 1 exit status Using rt_vsnprintf could avoid such problem.
-
- 14 9月, 2013 1 次提交
-
-
由 Grissiom 提交于
Either RT_EVENT_FLAG_AND or RT_EVENT_FLAG_OR should be set in the option flag. If none of them is present, the waiting thread will never be resumed.
-
- 19 8月, 2013 1 次提交
-
-
由 Grissiom 提交于
When print the thread names, we should use "%.*s" instead of bare "%s".
-
- 22 7月, 2013 1 次提交
-
-
由 bernard 提交于
-
- 15 7月, 2013 1 次提交
-
-
由 Grissiom 提交于
When realloc a bigger space and the next node is free and big enough, we should directly relocate the next node instead of doing alloc/memcpy. The new method not only faster in this cases, it would avoid memory fragment as well.
-
- 11 7月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 09 7月, 2013 1 次提交
-
-
由 Grissiom 提交于
This is a simple work around to the current device stack design. A ref_count could let different modules to open/close the same device independently without interfere others in some degree. But there is still some data shared between the modules, like flag, open_flag and user_data. Moreover, it won't yield an error if A open a device, and B read from it before open it in B. Maybe alloc a new handle in rt_device_open will be the ultimate solution. But that is much bigger change and we may leave it to future development.
-
- 29 6月, 2013 1 次提交
-
-
由 yiyue.fang 提交于
convert Tabs to spaces
-
- 24 6月, 2013 2 次提交
-
-
由 Bernard Xiong 提交于
-
由 Bernard Xiong 提交于
-
- 23 6月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 03 6月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 25 4月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 17 4月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 10 4月, 2013 1 次提交
-
-
由 yiyue.fang 提交于
2006 - 2013 Copyright by rt-thread team
-
- 23 3月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 17 1月, 2013 1 次提交
-
-
由 Grissiom 提交于
If two timer will timeout at the same tick, the one started later will be called later. I've tested the patch on simulator and it _seems_ OK. Reported-by:
xdzy on the forum and delin17 <delin17@qq.com>
-
- 08 1月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 31 12月, 2012 1 次提交
-
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2569 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
- 29 12月, 2012 1 次提交
-
-
由 bernard.xiong@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2554 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
- 25 12月, 2012 9 次提交
-
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2527 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2526 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2525 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2524 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2523 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2522 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2521 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2520 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 bernard.xiong 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2519 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
- 22 12月, 2012 1 次提交
-
-
由 bernard.xiong@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2507 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
- 21 12月, 2012 2 次提交
-
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2506 bbd45198-f89e-11dd-88c7-29a3b14d5316
-
由 dzzxzz@gmail.com 提交于
git-svn-id: https://rt-thread.googlecode.com/svn/trunk@2505 bbd45198-f89e-11dd-88c7-29a3b14d5316
-