<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rt-thread.git/components/drivers/src/pipe.c, branch v3.0.0</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/rt-thread.git/atom/components/drivers/src/pipe.c?h=v3.0.0</id>
<link rel='self' href='http://cgit.235523.xyz/rt-thread.git/atom/components/drivers/src/pipe.c?h=v3.0.0'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/'/>
<updated>2017-10-17T14:27:06Z</updated>
<entry>
<title>[libc] Add RT_USING_POSIX macro.</title>
<updated>2017-10-17T14:27:06Z</updated>
<author>
<name>bernard</name>
<email>bernard.xiong@rt-thread.com</email>
</author>
<published>2017-10-17T14:27:06Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=8a38307e2cce628017e9eb7153ae7a2430a3d9ef'/>
<id>urn:sha1:8a38307e2cce628017e9eb7153ae7a2430a3d9ef</id>
<content type='text'>
1. Add macro check in rtdebug.h;
2. Use RT_USING_POSIX for poll/select, stdin etc.
3. Split dfs_posix.h to dfs_posix.h, dfs_poll.h and dfs_select.h;
</content>
</entry>
<entry>
<title>[components][drivers] Check macro "RT_USING_DFS" when using DFS relative method/functions.</title>
<updated>2017-10-16T07:12:35Z</updated>
<author>
<name>ArdaFu</name>
<email>pengfei.fu@gmail.com</email>
</author>
<published>2017-10-16T07:12:35Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=fc7abc658013d326d47145f85402cead0728b1a0'/>
<id>urn:sha1:fc7abc658013d326d47145f85402cead0728b1a0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[DeviceDrivers] change cmd type.</title>
<updated>2017-10-15T14:56:46Z</updated>
<author>
<name>bernard</name>
<email>bernard.xiong@rt-thread.com</email>
</author>
<published>2017-10-15T14:56:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=d7087fdd3b998192afb03b34fd8034071d06bde7'/>
<id>urn:sha1:d7087fdd3b998192afb03b34fd8034071d06bde7</id>
<content type='text'>
1. Change 'rt_uint8_t' type of cmd to 'int';
2. Add waitqueue;
3. Split device ipc header files;
</content>
</entry>
<entry>
<title>device/pipe: add a control cmd to get the space left in pipe</title>
<updated>2013-10-22T17:43:18Z</updated>
<author>
<name>Grissiom</name>
<email>chaos.proton@gmail.com</email>
</author>
<published>2013-10-22T17:43:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=0feefc03b6008301a19a430427390cc9c44decf8'/>
<id>urn:sha1:0feefc03b6008301a19a430427390cc9c44decf8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>dev/pipe: make pipe a type of device</title>
<updated>2013-08-20T02:16:55Z</updated>
<author>
<name>Grissiom</name>
<email>chaos.proton@gmail.com</email>
</author>
<published>2013-08-20T02:16:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=7e68096a88aaa9279507df54da191893be99f7df'/>
<id>urn:sha1:7e68096a88aaa9279507df54da191893be99f7df</id>
<content type='text'>
Pipe have many differences with char device. The main difference is
altough pipe have both read and write, it is unidirectional in nature.
</content>
</entry>
<entry>
<title>dev/pipe: cleanup</title>
<updated>2013-08-19T08:25:17Z</updated>
<author>
<name>Grissiom</name>
<email>chaos.proton@gmail.com</email>
</author>
<published>2013-08-19T08:25:17Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=0340300f89a924b30fd8042b76686a236720d3d7'/>
<id>urn:sha1:0340300f89a924b30fd8042b76686a236720d3d7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>dev/pipe: call rx_indicate the time we resume reader</title>
<updated>2013-08-19T07:57:59Z</updated>
<author>
<name>Grissiom</name>
<email>chaos.proton@gmail.com</email>
</author>
<published>2013-08-19T07:57:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=e8cca2315a790d61c743a71e1a682e6ace7866fd'/>
<id>urn:sha1:e8cca2315a790d61c743a71e1a682e6ace7866fd</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>device/pipe: add nonblocking read/write and force write mode</title>
<updated>2013-08-19T07:35:56Z</updated>
<author>
<name>Grissiom</name>
<email>chaos.proton@gmail.com</email>
</author>
<published>2013-08-19T07:35:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=d683d32bd5502c15be600145966400a41710a7f4'/>
<id>urn:sha1:d683d32bd5502c15be600145966400a41710a7f4</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>device/pipe: add rt_pipe_{init,detach}</title>
<updated>2013-08-19T04:28:59Z</updated>
<author>
<name>Grissiom</name>
<email>chaos.proton@gmail.com</email>
</author>
<published>2013-08-19T04:24:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=38ce3879d8a98827338696e0b326ba6f6b1749f7'/>
<id>urn:sha1:38ce3879d8a98827338696e0b326ba6f6b1749f7</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Embedded GPLv2 license in drivers</title>
<updated>2013-06-27T16:36:54Z</updated>
<author>
<name>yiyue.fang</name>
<email>dzzxzz@gmail.com</email>
</author>
<published>2013-06-27T16:36:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=621fbdb90c9f9529700ed8894b01919ac1ec1929'/>
<id>urn:sha1:621fbdb90c9f9529700ed8894b01919ac1ec1929</id>
<content type='text'>
</content>
</entry>
</feed>
