- 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.
-
- 08 9月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 04 9月, 2013 2 次提交
-
-
由 Bernard Xiong 提交于
sim/posix: move rt_hw_context_switch_interrupt after it's definition
-
由 Grissiom 提交于
This fix a compile error in Clang.
-
- 03 9月, 2013 4 次提交
-
-
由 Bernard Xiong 提交于
stm32f10x: fix the rtgui initialization
-
由 Grissiom 提交于
The rtgui_system_server_init prototype is wrong. And if we use RT_USING_COMPONENTS_INIT, there is no need to call rtgui_system_server_init again.
-
由 Bernard Xiong 提交于
log_trace: cleanup
-
由 Grissiom 提交于
-
- 02 9月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
finsh: use alias in the variable definition
-
- 01 9月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
Simulator linux
-
- 31 8月, 2013 3 次提交
-
-
由 Grissiom 提交于
With this patch, one could define two alias for the same function like: FINSH_FUNCTION_EXPORT_ALIAS(rt_hw_cpu_reset, reboot, reboot the cpu); FINSH_FUNCTION_EXPORT_ALIAS(rt_hw_cpu_reset, __cmd_reboot, reboot the cpu); Suitable for being used in MSH/Finsh.
-
由 Grissiom 提交于
SDL may use DFS to open files. It should be run after rt_components_init.
-
由 Grissiom 提交于
rt_hw_sdl_start should wait untill the rtgui_graphic_set_device is called int the sdl_loop. Use pthread_cond_wait to achieve this in Linux.
-
- 27 8月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
Some fix for the portal device
-
- 22 8月, 2013 2 次提交
-
-
由 Grissiom 提交于
When forwarding rx/tx callback from the underlaying device(pipe), the "dev" argument should be the portal. So the portal callback could think itself as called.
-
由 Grissiom 提交于
It does not make sense to open portal without a flag. One should open a portal with RT_DEVICE_OFLAG_RDWR in most cases.
-
- 21 8月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
finsh/cmd: add description for new pipe and portal device
-
- 20 8月, 2013 4 次提交
-
-
由 Grissiom 提交于
-
由 Bernard Xiong 提交于
Portal device
-
由 Grissiom 提交于
Portal is a device that connect devices. Currently, you can only connect pipes in portal. Pipes are unidirectional. But with portal, you can construct a bidirectional device with two pipes.
-
由 Grissiom 提交于
Pipe have many differences with char device. The main difference is altough pipe have both read and write, it is unidirectional in nature.
-
- 19 8月, 2013 13 次提交
-
-
由 Bernard Xiong 提交于
Ringbuffer and Pipe
-
由 Grissiom 提交于
-
由 Grissiom 提交于
Some reader(FinSh again) would like to block on a semaphore which is released in rx_indicate. So we should invoke rx_indicate in _rt_pipe_resume_reader.
-
由 Grissiom 提交于
The previous implementation will always blocks the reader/writer. However, at least FinSh would expect the device to be nonblocking --- read should return 0 when there is no data in it.
-
由 Grissiom 提交于
Add the APIs that will discard the old data when rb is full.
-
由 Grissiom 提交于
RT_RINGBUFFER_SIZE could mean "the size of the whole buffer", "the size of the empty space" or "the size of the data". Moreover, it's never a micro anymore. Change it to rt_ringbuffer_data_len before it's too late. Also, RT_RINGBUFFER_EMPTY is changed to rt_ringbuffer_space_len.
-
-
由 Bernard Xiong 提交于
device/pipe: add rt_pipe_{init,detach}
-
-
由 bernard 提交于
-
由 Grissiom 提交于
This provide the possibility that allocate the buffer of the ringbuffer on a specific region, instead of always mallocing it. It also bring us the benefit of using pipe device on the systems without heap.
-
由 Bernard Xiong 提交于
fix debug output of scheduler
-
由 Grissiom 提交于
When print the thread names, we should use "%.*s" instead of bare "%s".
-
- 12 8月, 2013 2 次提交
-
-
-
由 Bernard Xiong 提交于
-
- 09 8月, 2013 1 次提交
-
-
由 bernard 提交于
-
- 30 7月, 2013 2 次提交
-
-
-
由 Bernard Xiong 提交于
SEP6200 Support
-
- 29 7月, 2013 1 次提交
-
-
由 bernard 提交于
-