- 16 2月, 2014 1 次提交
-
-
由 qiuyiuestc 提交于
Pass USB CV test verification; Code cleanup;
-
- 30 12月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 29 12月, 2013 1 次提交
-
-
由 bernard 提交于
-
- 25 10月, 2013 3 次提交
- 23 10月, 2013 1 次提交
-
-
由 Grissiom 提交于
-
- 24 9月, 2013 1 次提交
-
-
由 joyhope 提交于
*buffer) with buffer pointer
-
- 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.
-
- 20 8月, 2013 2 次提交
-
-
由 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 6 次提交
-
-
由 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.
-
由 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.
-
- 25 7月, 2013 1 次提交
-
-
由 reynoldxu 提交于
-
- 24 7月, 2013 2 次提交
- 29 6月, 2013 1 次提交
-
-
由 yiyue.fang 提交于
-
- 28 6月, 2013 2 次提交
-
-
由 yiyue.fang 提交于
-
由 yiyue.fang 提交于
-
- 23 6月, 2013 1 次提交
-
-
由 Bernard Xiong 提交于
-
- 15 6月, 2013 1 次提交
-
-
由 heyuanjie87 提交于
-
- 11 6月, 2013 1 次提交
-
-
由 Grissiom 提交于
Some driver will emit USB_MSG_DATA_NOTIFY before the USB get configured. Filter out those events.
-
- 06 6月, 2013 1 次提交
-
-
由 Grissiom 提交于
When the core received an USB_MSG_PLUG_OUT event, it will stop all the classes. This make a chance that the classes could get rid off doing useless stuff while the USB cable is plugged out.
-
- 30 5月, 2013 1 次提交
-
-
由 heyuanjie87 提交于
-
- 25 5月, 2013 3 次提交
-
-
由 weety 提交于
-
由 qiuyiuestc 提交于
When the USB got RESET packet from the host and the address is setup, all the classes will got reset. The reset is done by class stop and than class run. So the classes should reset their internal state in class_{run,stop}. Besides, the USB device driver could post a USB_MSG_RESET message on every RESET packet.
-
由 Grissiom 提交于
Reset the vcom state in class_{run,stop} and when the PC is not receiving data from me.
-
- 23 5月, 2013 1 次提交
-
-
由 heyuanjie87 提交于
-
- 17 5月, 2013 4 次提交
-
-
由 wuyangyong 提交于
-
由 wuyangyong 提交于
-
由 wuyangyong 提交于
-
由 heyuanjie87 提交于
-
- 12 5月, 2013 3 次提交
-
-
由 Grissiom 提交于
Although currently the only message send to the queue is struct udev_msg, in order to keep backward compacity and for extention in the future, we set the size of message to 32.
-
由 Grissiom 提交于
It also add two configurations for the USB device even loop thread: RT_USBD_THREAD_STACK_SZ to set the stack size, default to 2048 RT_USBD_THREAD_PRIO to set the priority, default to 8 You can overwrite the default values in rtconfig.h
-
由 Bernard Xiong 提交于
-